Attachment 20 DD1494_PreparationGuide.pdf
PDF 2 MB Posted
- Attached to
- Family of Weapon Sight – Individual (FWS-I) Full Rate Production Federal contract opportunity
- Solicitation number
- W91CRB-21-R-0012
About this file
This is a solicitation for the Family of Weapon Sights - Individual (FWS-I) Full Rate Production contract. The Army is seeking the production of FWS-I units, associated spare parts, maintenance, and technical support. The FWS-I is an uncooled, lightweight infrared imaging device of medium to high resolution used for surveillance and target acquisition on individual weapons during all lighting conditions. When paired with an Intra-Soldier Wireless device, the FWS-I will provide a wireless Rapid Target Acquisition capability. When paired with a Direct View Optic, the FWS-I will provide interconnectivity such that its displayed imagery serves as input to the DVO. The government emphasizes adherence to schedules, integration, qualification, and intellectual property rights.
View the file
Other files for this federal contract opportunity
Show all 46
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DD Form 1494 Preparation Guide
INTRODUCTION
A principal goal of the DoD’s spectrum management program is to develop and efficiently manage the DoD’s use of the spectrum during the frequency allocation, allotment, and assignment processes. Achieving this goal minimizes the potential for interference during the fielding and employment of spectrum dependent equipment. The Frequency Allocation-to-Equipment Process supports the DoD’s spectrum management goal. Achievement of this goal is critical due to significant increases in the use of the available electromagnetic spectrum due to technological advancements and spectrum being reallocated away from military use, or being opened to sharing with commercial use.
DoD acquisition policy states that the funds for the acquisition, research, development, production, purchase, lease, or use of weapons systems, information management systems, electronic warfare (EW) systems, or other systems that require use of the electromagnetic spectrum will not be released by the obligating authority until an application for frequency allocation has been approved.
In the research, development, production and procurement cycles, adherence to acquisition policy must begin as early as possible. This process includes policies, responsibilities, and procedures for Army commands, agencies, and the Program Executive Officers (PEOs) and Product Managers (PMs) involved in conceptualizing research, development, production, procurement, modification/product improvement, and the leasing of spectrum dependent equipment.
The Frequency Allocation-to-Equipment Process is a spectrum requirement and exists to determine
(1) if equipment can operate in spectrum bands per the national and international tables of spectrum allocation; and that
(2) equipment being brought into the Army inventory conforms to applicable spectrum management regulations, directives, standards, and specifications.
For almost 50 years, the Joint Frequency Panel of the United States Military Communications-Electronics Board (MCEB) has reviewed the characteristics of radio frequency (RF) equipment purchased, or developed, by the Department of Defense (DoD). This review process is called the Joint Frequency Allocation-to- Equipment Process, or as it is commonly known, the J-12 Process.
The form currently used to submit systems information to the MCEB for frequency allocation approval is the DD Form 1494, last revised in August 1996.
All major military RF systems, as defined in Chapter 10 of the National Telecommunications and Information Administration (NTIA) Manual of Regulations & Procedures for Federal Radio Frequency Management, are reviewed in parallel with the J-12 process by the Interdepartment Radio Advisory Committee (IRAC) Spectrum Planning Subcommittee (SPS).
The Chief Information Officer (CIO) G6 Staff has the responsibility to review, coordinate, and approve applications for frequency allocations submitted by Army activities. Within the Army, that function has been assigned to the Army Spectrum Management Office (ASMO).
The submission of incomplete and inaccurate DD Form 1494 applications consumes unnecessary manpower and causes processing delays. A review of past DD Form 1494 submissions by the PM AIT and the JSC suggests that the information being sought and the correct method of presenting that information is sometimes unclear.
To minimize problems encountered when DD Form 1494 applications are submitted, the PM Automated Information Technology (PM AIT) office requested that the Joint Spectrum Center (JSC) update and prepare an electronic version of the “Preparation Guide” for completing the DD Form 1494.
ABOUT THIS GUIDE
This guidebook is divided into seven sections: Introduction, General Instructions, Guide to the DD Form 1494 Pages, Sample Completed DD Form 1494s, More About, Points of Contact, and References.
The Introduction provides background on the Allocation-to-Equipment Process and the DD Form 1494 requirement.
The General Instructions section provides detailed instructions and a template for filling out the DD Form 1494.
The Sample Completed DD Form 1494s section contains two examples of completed and reviewed DD Form 1494s. One is for a Radio Frequency Identification (RFID) system and the other is for a Wireless Local Area Network (LAN) application.
The More About… section includes comprehensive information about specific aspects of the DD Form 1494 fields.
The remaining sections provide Points of Contact, and a list of additional References.
GENERAL INSTRUCTIONS
The DD Form 1494 Preparation Guide is an Adobe Acrobat 6.0 PDF document.
To take advantage of the features of this document, download, at no cost, Adobe Acrobat Reader (6.0, or greater), available from http://www.adobe.com
The technical specifications of the spectrum dependent equipment must be obtained prior to starting this process. Transmitter, receiver, and antenna characteristics of the proposed system are also required. In some cases, access to a measurement lab will be required to obtain this information. Please note that for Federal Communications Commission (FCC) Part 15 Type Accepted equipment, an FCC test report can provide some of this information. For commercial off-the-shelf (COTS) equipment, manufacturer technical specifications provide a significant source of data to complete the DD Form 1494.
GUIDE TO THE DD FORM 1494 PAGES
The DD Form 1494 is composed of six basic pages and a system line diagram.
The main pages are titled:
• DoD General Information
• Transmitter Equipment Characteristics
• Receiver Equipment Characteristics
• Antenna Equipment Characteristics
• NTIA General Information
• Foreign Coordination General Information.
If the proposed system will operate only within the United States & Possessions (US&P), all pages, except the Foreign Coordination page, must be completed.
The Foreign Coordination page is only required if the planned system will operate outside of the US&P.
On the inside left of the DD Form 1494 Preparation Guide is a set of bookmarks that can be used to navigate through the Guide. The actual document contents are found on the right (see Figure 1).
Begin processing a DoD General Information page by positioning the mouse and clicking on the ‘+’ sign located to the left of the field “DoD General Information.”
This will expand the field descriptions for the DoD General Information Page as shown in Figure 2.
Figure 1
Figure 2
Click on each topic for instructions for each field. (See Figure 3.)
Figure 3
Scroll to the bottom of the page to view pages titled Common Errors and More About.
Common Errors describes the most common mistakes made on DD Form 1494s. These mistakes can lead to delays in obtaining equipmente certification.
More About provides hot links for a more in depth review of the word or phrase selected. Simply click on the word or phrase to be directed to the additional reference sources.
Blank forms are provided and should be completed using the required data.
Note: While the free, downloadable Adobe Acrobat Reader will permit the user to enter data on the DD 1494 Forms and to print the completed forms, it will not permit the user to save that information. To save the data, the user must obtain a copy of the fully-licensed product: Adobe Acrobat 6.0.
To navigate back to the DD Form 1494, simply click the Previous View button on the bottom of the Adobe reader. (See Figure 4.)
Figure 4
APPLICATION FOR EQUIPMENT
FREQUENCY ALLOCATION
CLASSIFICATION DATE Form Approved OMB No. 0704-0188
PAGE 1 OF
The public reporting burden for this collection of information is estimated to average 24 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0704-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.
PLEASE DO NOT RETURN YOUR FORM TO THE ABOVE ADDRESS. RETURN COMPLETED FORM TO THE USING AGENCY OR CONTRACTING AGENCY, AS
APPROPRIATE.
DOD GENERAL INFORMATION
TO FROM
1.
2. NOMENCLATURE
3. (X one)
a. STAGE 1 - CONCEPTUAL b. STAGE 2 - EXPERIMENTAL c. STAGE 3 - DEVELOPMENTAL d. STAGE 4 - OPERATIONAL
4. REQUIREMENTS
a. FREQUENCY(IES)
b. EMISSION DESIGNATOR(S)
5. TARGET STARTING DATE FOR SUBSEQUENT STAGES
a. STAGE 2 b. STAGE 3 c. STAGE 4
6. OF USE
7. AREA FOR
a. STAGE 2
b. STAGE 3
c. STAGE 4
8. OF UNITS
a. STAGE 2 b. STAGE 3 c. STAGE 4
9. OF UNITS OPERATING SIMULTANEOUSLY IN THE SAME ENVIRONMENT
10. OTHER J/F 12 APPLICATION NUMBER(S) TO BE
a. SUPERSEDED J/F 12/ b RELATED J/F 12/
11. IS THERE ANY OPERATIONAL REQUIREMENT AS DESCRIBED IN
THE INSTRUCTIONS FOR PARAGRAPH 11?
a. YES b. NO c. NAvail
12. NAMES AND TELEPHONE NUMBERS
a. PROGRAM MANAGER (1) COMMERCIAL (2) AUTOVON
b. PROJECT ENGINEER (1) COMMERCIAL (2) AUTOVON
13. REMARKS
DOWNGRADING INSTRUCTIONS CLASSIFICATION
PAGES
APPLICATION TITLE
SYSTEM
STAGE OF ALLOCATION
FREQUENCY
EXTENT
GEOGRAPHICAL
NUMBER
NUMBER
DD FORM 1494, AUG 96 (EG) PREVIOUS EDITION MAY BE USED. Designed using Perform Pro, WHS/DIOR, Aug 96
DOD GENERAL INFORMATION
CLASSIFICATION
If the multi-page DD Form 1494 contains classified information, it must be handled in accordance with appropriate agency security directions. For the US Army, the DD Form 1494 classification level shall be in accordance with DoD Directive 5200.1-R and US Army Information Security Program Regulation
AR 380-5.
For classified applications, the highest classification for each item, or sub-item, must be indicated by a (U) for UNCLASSIFED, (C) for CONFIDENTIAL, or (S) for SECRET, alongside the item, or sub-item, title. Downgrading instructions must be indicated.
Frequently, individual pages are classified in different ways. For example, a system might have SECRET data on the Transmitter and Receiver Equipment Characteristics pages, CONFIDENTIAL data on the Antenna Equipment Characteristics page, and UNCLASSIFED data on the other pages. In this case, the overall classification is SECRET, and each page is marked with the highest security classification indicated on that page. Each page has a classification block at the top and bottom and the appropriate terms (UNCLASSIFIED, CONFIDENTIAL, or SECRET) should be typed into those blocks.
If a page is classified as CONFIDENTIAL or SECRET, every block on that page shall be marked with its appropriate classification, based on the data entered in that block. This block-by-block marking should conform to the portion marking, as defined in DoD Directive 5200.1-R.
The overall (highest) classification of the document must be conspicuously stamped on the top and bottom of the front page and the top and bottom of the back of the last page. If the front page has a classification that is lower than the overall classification, the classification block at the top and bottom of the front page must reflect the classification of the page (e.g., "This Page is UNCLASSIFIED," or "This Page is CONFIDENTIAL," etc., in addition to the overall classification stamp.
The application title (Item 1 of the DoD, NTIA, and Foreign Coordination General Information pages) should never be classified.
The terms "Competition Sensitive" or "Proprietary Data" are not classifications and, therefore, should not be entered into the classification block. If needed, the words "Competition Sensitive" or "Proprietary Data" should be typed within the top and bottom margins of the form, and/or stamped in the REMARKS block.
The J-12 process is designed to handle and protect proprietary data. No proprietary data will be abstracted, or entered into any reports, or data bases, not directly involved with the J-12 process. A designation of “Competition Sensitive” may only be applied when two or more contractors are bidding for a contract, and should be removed within a reasonable time period. After contract award, the data on the successful contractors' DD Form 1494 will not be considered proprietary.
Common Errors: Classification is not entered on the form.
More About: DoD Directive 5200.1-R, AR 380-5
DATE
Enter the application date. Include the Day, Month, and Year. Examples:
15 July 2004, or 15/07/2003.
Common Errors: The date field is left blank.
PAGE NUMBER
Enter the page number. The DoD General Information page is always page 1, and is preprinted "Page 1 of Pages." The total number of pages should be inserted in the space provided. The correct number to insert is the total number of equipment characteristics pages (transmitter, receiver, and antenna), plus two (for the DoD and NTIA General Information pages), plus the number of continuation pages, line diagram pages, and space systems data pages.
Common Errors: Page numbering is not a common problem. The US Army DD Form 1494 processing office often re-numbers the pages before submitting them to the MCEB.
Three DD 1494 pages (DoD General Information, NTIA General Information, and Foreign Coordination General Information) have “Downgrading Instructions” blocks at the bottom. The downgrading instructions for the information presented must be supplied for classified systems. All downgrading instructions must conform to the requirements of DoD Directive 5200.1-R and AR 380-5. For unclassified systems the entry “NA” is applicable.
TO
Enter the addressee for US Army DD Form 1494 submissions. The current addressee is:
US ARMY NETWORK ENTERPRISE TECHNOLOGY COMMAND
Attn: James Thomas 2461 Eisenhower Ave., Suite 1204 Alexandria, VA 22331-2200 Phone: 703-325-8227 DSN 221-8227
The e-mail address for submitting US Army DD Form 1494 applications is:
James.E.Thomas@us.army.mil
The e-mail address for classified US Army DD Form 1494 applications is:
Thomas3J@ncr.disa.smil.mil
Common Errors: Electronic delivery of these applications must be accompanied by an electronic signature of the government representative making the request for spectrum certification
FROM
This block should include the mailing address of the government office originating the DD Form 1494. This may be the command that is procuring, developing, modifying, or using the equipment. This block should not contain the address of a government contractor.
Common Errors: Required information is not provided, or the mailing address is not correct.
1. APPLICATION TITLE
Enter the Government’s nomenclature of the equipment, or enter the manufacturer’s name and model number, and a short descriptive title. If a Joint Electronics Type Designation System (JETDS) nomenclature (AN nomenclature) has been assigned to the RF component being allocated, it should be listed in this block along with the descriptive name of the equipment (e.g., AN/TPQ-37 Artillery Locating Radar). If a JETDS nomenclature is not assigned, a unique descriptive title must be entered (e.g., Symbol Technologies Spectrum 24 Wireless). In the case of commercially produced off-the-shelf equipment, the title should include the manufacturer’s name and model number, in addition to a short descriptive title (e.g., SAVI Model STR7200 Hand-Held Interrogator, Reader Module).
If multiple equipment are allocated, this should be reflected in the Application Title block. Example: “SAVI EchoPoint System” would be a correct entry. The manufacturer’s name is not important in the case of competition sensitive equipment; it is perfectly acceptable to omit this information. Instead, the identifier “Model A” or “Contractor B” should be substituted.
Note: “Title” and “Nomenclature not yet assigned” are not acceptable entries.
Note: The Application Title blocks on the NTIA General Information and Foreign Coordination pages must be identical to the information listed on the DoD General Information page.
Common Errors: The JETDS nomenclature (if available) is not included in the title. For COTS equipment, the equipment manufacturer’s name and model number is not provided in the title.
More About: JETDS
2. SYSTEM NOMENCLATURE
Enter the nomenclature of the overall system for which this equipment is a subsystem (e.g., Ammunition Automatic Identification Technology (AMMO AIT), Patriot, or Global Positioning System).
The System Nomenclature is a title describing the system requiring the allocated RF elements. In cases where an allocation is needed for a complex system made up of several subsystems, a separate DD Form 1494 must be submitted for each separate subsystem. For example, the Airborne Adverse Weather Weapon System (AAWWS) has two distinct RF components: the RF Hellfire Modular Missile System and the Fire Control Radar. An application for allocation for the AAWWS would require one form for the RF Hellfire Modular Missile System and one for the Fire Control Radar. Both of the DD Form 1494s would list the system nomenclature as the AAWWS, but the entry in Item 1, Application Title, would be different, depending on the subsystem being allocated.
Note: Because the two applications are related, each application should show the J/F 12 number of the other application in Item 10b of Page 1.
For less complex systems, the Application Title and System Nomenclature may be identical. In this case, the same entry as in Item 1, APPLICATION TITLE, should be inserted. Leaving this block blank may lead to confusion as to the exact relationship, or lack thereof, between this allocation application and a similar one.
Equipment should be addressed on an "RF link" rather than "platform" basis.
Normally, each link is considered separately. For example, an air-launched guided missile might have two RF links: a Telecommand (aircraft-to-missile) link and a Video (missile-to-aircraft) link. Each of these RF links should be addressed separately, and should include one transmitter, one receiver, and one, or more, antenna characteristics pages. The data on the technical characteristics pages should be related, as they all pertain to one RF link (one set of equipment designed to function together). If the equipment is allocated on a platform basis, each allocation would still have one, or more, transmitter, receiver, and antenna page, and the only relationship would be the physical location of the equipment. A missile allocation would have the video transmitter with its associated antenna; and the telecommand receiver with its associated antenna. Obviously, allocations on an RF link basis present a clearer picture than allocations on a platform basis and are, therefore, less confusing.
Common Errors: System nomenclature information is not provided.
3. STAGE OF ALLOCATION
Stages of allocation correspond to the stages of life cycle management. The amount and type of data required on the DD Form 1494 vary with the stage of allocation. Read the general NTIA description of each stage, given below, and mark the appropriate block.
STAGE-1 - CONCEPTUAL. Initial planning has been completed, including proposed frequency bands and other available characteristics. A conceptual allocation is required prior to releasing funds for studies, or assembling “proof-of-concept” test-beds. Planned or estimated details concerning the equipment should be entered on the DD Form 1494. Where information has not been determined, the entry “NAvail” or "Not Available" should be used. Stage-1 is for system planning and does not involve actual transmission or reception.
STAGE-2 - EXPERIMENTAL. The preliminary design has been completed; on-air radiations, using test equipment or preliminary models, may be required.
Prior to the release of funds, an experimental allocation is required for building a radiating test model, or assignment of a frequency for experimental usage, including, but not limited to, units tested within a laboratory. Estimated and calculated data can be used, where appropriate, for nearly all DD Form 1494 technical items.
STAGE-3 - DEVELOPMENTAL. The major design has been completed;
radiation may be required. Prior to release of funds for engineering development models, a Stage-3 allocation must be obtained. All applicable items of the DD Form 1494 should be filled in with measured data. Where measured data are not available, calculated data can be substituted. An entry of “NAvail” or “Not Available” must include a reason.
STAGE-4 - OPERATIONAL. Development has been essentially completed and final operating constraints required to assure compatibility need to be identified.
Prior to release of funds for production units, an operational frequency allocation is mandatory. Measured data for all technical characteristics such as emission bandwidth, harmonic level, spurious level, etc., should be provided when submitting a Stage-4 frequency allocation application.
All COTS equipment with unmodified RF characteristics fall into this type of allocation. Although the equipment may be used within experimental or developmental systems, by definition, it is operational equipment, because of its off-the-shelf status (for example, an off-the-shelf telemetry system used during development of a missile).
Common Errors: COTS equipment submitted as other than Stage-4. However, if COTs equipment is modified in any way, a Stage-2 or -3 application should be submitted.
More About: Data requirements for each stage
4. FREQUENCY REQUIREMENTS
4.a. Enter the required frequency band(s), indicating units, (e.g., kHz, MHz, or GHz). For equipment designed to operate only at a single frequency, enter this frequency and units.
4.b. Enter the emission designator(s), including the necessary bandwidth for each designator, as described in Chapter 9 of the NTIA manual (e.g., 40M0PON). For systems with a frequency hopping mode, identify each mode as “hopping” or “non-hopping” (e.g., 64M0F3E Hopping).
Enter other information pertinent to frequency requirements, such as minimum frequency separation or special relationships involving multiple discrete frequencies in Block 13, titled REMARKS.
Common Errors: Frequencies are not submitted. The frequency bands requested do not support the planned radio service. Emission designator is often left out. Lockouts have not been identified in the REMARKS section.
More About: Emission Designators, Frequencies, Lockouts
5. TARGET STARTING DATE FOR SUBSEQUENT STAGES
For each subsequent stage, enter the proposed date of application submission.
These dates mark when various life-cycle management phases of the equipment are scheduled to begin. A projected date for the start of all future phases should be provided in the blocks. An “NA” or “Not Applicable” should be entered on the line for current and accomplished phases. For example: A system moving from the current Advanced or Engineering Development stage to the Operational or Production stage in November of 2005 will list on the DD Form 1494 "NA" for STAGES 2 and 3 and "November 2005" for STAGE-4.
Occasionally, equipment is developed that was never intended to be introduced into the operational inventory (e.g., a proof-of-concept test bed, or a one-of-a-kind piece of laboratory equipment). Indicate this on the DD Form 1494 by entering an "NA" for the STAGE-4 date and including an explanation in Block 13, REMARKS.
Common Errors: Dates are not in correct sequence. Dates for the stage have already past.
More About: Life-cycle management, COTS Equipment
6. EXTENT OF USE
Describe the extent of use, continuous or intermittent, that will apply to Stage-4.
If intermittent, an estimate of the total time of equipment operation should be given. For equipment intended primarily for peacetime use, this should include the number of hours per day, and days per week. For weapons systems and wartime-oriented systems, an estimated number of hours of operation per mission should be given. Most equipment (wartime systems included) have some use in a training role that should also be listed in this block. A sample entry in this block would read "Peacetime training, testing, and use will include approximately 2 hours per day, 5 days per week of intermittent transmissions.
During wartime, system will operate at all times with intermittent 1-minute transmissions, approximately 10 per hour."
Common Errors: Information not supplied.
7. GEOGRAPHICAL AREA FOR
Enter geographic location(s), or area(s) of use, for this stage and subsequent stage(s). Provide geographical coordinates (degrees, minutes, seconds), if available. Enter "NA" for all accomplished stages.
Stage-2 and -3
Whenever possible, specific sites, identified by geographic location and coordinates should be listed. When a large number (e.g., >10) of US test sites are anticipated, but the final sites have not been chosen, it is acceptable to add "and various other test sites in the US&P."
All test sites outside the Continental United States (OCONUS) should be identified by base, station or military unit name, and the country.
Stage-4
The locations of operations should be as specific as possible. For fixed equipment, in most cases, it should be possible to list the site locations by latitude and longitude. For mobile systems where no specific location can be identified, all of the countries where standard coordination is to be accomplished must be listed. General rather than specific locations lead to time-consuming questions throughout the review process.
If the space on the DD Form 1494 is too small to list all locations and specific sites, use the REMARKS section or continuation pages.
Common Errors: Organizations often do not know where the system will be operated. Entering “worldwide” is not acceptable; specific countries are needed.
The fewer locations to coordinate, the less time required for approval. Japan and Korea require specific geographic locations.
8. NUMBER OF UNITS
Enter the total number of units planned for the current allocation stage and for any remaining stages.
This item should be the sum of the number of units being built, procured, or used at each stage of allocation. If the number of transmitters differs from the number of receivers, they should be identified and listed separately. When there is a one-for-one correspondence of transmitters to receivers, a single figure may be listed.
Common Errors: Required data is not supplied.
9. NUMBER OF UNITS OPERATING SIMULTANEOUSLY IN THE
SAME ENVIRONMENT
Enter the total number of units planned to be operating simultaneously in the same environment during Stage-4 use.
The environment is defined as the physical area over which the equipment signal can communicate or interfere. For a fixed microwave radio, this may be two units, the transmitting station and the receiving station. For radars, there may be only a single radar in the environment. In the case of a base police radio net, there may be dozens of "handie-talkies" within reception range of each other.
When the number of systems operating may vary, a “normal” and a “maximum” value could also be given. The size of the area (e.g., geographical coordinate and a radius) should also be stated. The entry in Item 9 can never be "NA."
Common Errors: Required data is not submitted.
10. OTHER J/F 12 APPLICATION NUMBER(S) TO BE
Mark the appropriate boxes(s) and enter J/F 12 numbers for superseded and/or related applications.
BOX 10.A. SUPERSEDED
This is the box most often used when requesting a new allocation for an already allocated system. As a system transitions from conceptual to operational, it must be allocated at each stage. The title describes the action that will be taken by the USMCEB Frequency Panel and the Department of the Army. This block should also be used to indicate that the system being allocated is replacing an existing system. The system being replaced may continue to be operational, but until it is phased out of the inventory, it will still need a valid frequency allocation. Include the J/F 12 number to be superseded on the line to the right of the "Superseded J/F 12/" box. Write "None" when no system is being replaced.
BOX 10.B. RELATED
When two separately allocated systems are being used in conjunction with each other, such as a newly developed earth station and an existing space station, the space station's J/F 12 number should be entered opposite the checked box marked RELATED J/F 12. On the DD Form 1494, RELATED does not extend to different systems performing the same or similar purposes, unless the two systems work together. For example, the Motorola H34SX Hand Held and the General Electric MPD Series radios perform a voice communications function and have similar RF characteristics, but they are not RELATED.
Write "None" for new systems that have never been allocated and are not related to other systems.
Common Errors: Submitter indicates other systems that are not directly related to this application.
11. OPERATIONAL REQUIREMENT
If this equipment will operate with the same, or similar, equipment used by other US Military Services, DoD Components, US Government Agencies, or Allied Nations, mark “YES” and specify, the Services, Agencies or countries (to include the country’s services) in Box 13 REMARKS.
Common Errors : Answering “YES,” but providing no explanation in Box 13
REMARKS.
More About: Remarks
12. NAMES AND TELEPHONE NUMBERS
The name and telephone number (both Commercial and DSN) of the Program Manager and a Project Engineer are required to permit contact between the US Army reviewing office and the Project Office during allocation processing. An important reason for this contact is to obtain missing or incomplete information.
The "Project Engineer" should be somebody familiar with the RF parameters of the system and, where possible, the DD Form 1494. In addition to the two required contacts, it is not uncommon to list a contractor point of contact, if the equipment is being produced or developed by such a contractor. Unless otherwise specified, it is assumed that direct liaison is authorized with all contacts listed. When the organization and address of the Program Manager, and Project Engineer are different from the application originator, this fact should be supplied in the Block 13 REMARKS section.
Common Errors : Contractors are listed as primary points of contact. A Government POC is always required.
13. REMARKS
This block may be used as a continuation of any of the preceding blocks. The continued block, or blocks, should be identified by block number. If any of the DD Form 1494 is classified, the security classification of each item of information contained in the REMARKS block must be explicitly marked.
Any additional information that clarifies the function or operation of the equipment may be entered in this block.
Common Errors: Not including a reference number in the REMARKS block for one or more of the numbered blocks on the form.
CLASSIFICATION PAGE
TRANSMITTER EQUIPMENT CHARACTERISTICS
1. MANUFACTURER’S MODEL NO. 2. NAME
10. FILTER EMPLOYED (X one)
a. YES b. NO
8. DESIGNATOR(S)
13. MAXIMUM BIT RATE
19. POWER
a. MEAN
b. PEP
20. OUTPUT DEVICE
21. HARMONIC LEVEL
24. REMARKS
CLASSIFICATION
3. 4.
5. RANGE 6. OF TUNING
7. CHANNELING CAPABILITY
9. TOLERANCE
11. SPREAD SPECTRUM (X one)
a. YES b. NO
12. EMISSION BANDWIDTH (X and complete as applicable)
CALCULATED MEASURED
a. -3 dB
b. -20 dB
c. -40 dB
d. -60 dB
e. OC-BW
14. MODULATION TECHNIQUES AND CODING
15. MAXIMUM MODULATION FREQUENCY
16. PRE-EMPHASIS (X one)
a. YES b. NO
17. DEVIATION RATIO
18. PULSE CHARACTERISTICS
a. RATE
b. WIDTH
c. RISE TIME
d. FALL TIME
e. COMP RATIO
a. 2ND
b. 3RD
c. OTHER
22. SPURIOUS LEVEL
23. FCC TYPE ACCEPTANCE NO.
NOMENCLATURE, MANUFACTURER’S
EMISSION
TRANSMITTER INSTALLATION TRANSMITTER TYPE
TUNING METHOD
RF
FREQUENCY
DD FORM 1494, AUG 96
TRANSMITTER EQUIPMENT CHARACTERISTICS
1. NOMENCLATURE, MANUFACTURER’S MODEL NO.
Enter the Government assigned JETDS equipment nomenclature. If no AN nomenclature has been assigned, a manufacturer's model name, or part number, should be entered. The number should be easily identified by the manufacturer if inquiries are made by the government. If the transmitter has neither type of identifier, as may occur in a conceptual or experimental allocation action, enter the system name followed by the word "transmitter." In a multi-transmitter system, a nomenclature describing the purpose of each transmitter would be appropriate on each respective transmitter page (e.g., "Command Guidance System (CGS) Projectile Subsystem Transmitter" and "Command Guidance System (CGS) Ground Subsystem”). Under no circumstances is the entry "None" or "Not Yet Assigned" acceptable.
Common Errors: Form is submitted without either the Government assigned nomenclature or manufacturer’s model number or part number.
More About: JETDS
2. MANUFACTURER’S NAME
Enter the manufacturer’s name, if available. Even if a manufacturer’s model number is listed in Item 1 (Nomenclature, Manufacturer’s Model No.) this block must still be completed. If the development is solely within an Army R&D element, it is appropriate to list the name of the organization in this block. In the case where a manufacturer has not been selected, as may occur in a conceptual (Stage-1) system, an entry of "NAvail" is acceptable here.
Common Errors: Manufacturer’s subsidiary name is given, rather than that of the parent company.
More About: Manufacturer’s
3. TRANSMITTER INSTALLATION
List the specific type(s) of vehicle(s), ship(s), plane(s), building(s), etc., where the transmitter will be installed. Include the platform(s) on which the transmitter is mounted (e.g., attached to a building, attached to a shipping container, a fixed site atop a mountain, an S-120 shelter, on a High Mobility Multipurpose Wheeled Vehicle (HMMWV), aboard a helicopter, etc.). All military vehicles should be identified by their proper military nomenclature. If the system is portable and not mounted in a vehicle, the user should be identified (e.g., man-portable carried by military police, hand held reader used by logistics personnel, or a handie-talkie worn by flight deck crew or by base police).
Common Errors: Required information is not supplied.
4. TRANSMITTER TYPE
Enter the generic class of the transmitter. The general modulation type and transmitter purpose should be entered as a two- or three-word description.
Examples are: FM Communications, Pulse Doppler Radar, 802.11b Wireless LAN, FSK Data Communications, Spread-spectrum Communications, etc. As shown in the examples, the format is "general modulation type" followed by "purpose." An entry of "NAvail" or "NA" is unacceptable.
Common Errors: Required information is not supplied.
5. TUNING RANGE
Enter the frequency range (e.g., 225-400), and units (e.g., kHz, MHz or GHz) over which the transmitter is capable of being tuned. For equipment designed to operate only at a single frequency, enter this frequency.
The entry should be the lowest tunable center frequency through the highest tunable center frequency. As a matter of convention, this tuning range does not include the transmitter's emission bandwidth.
If the transmitter is normally not tunable (e.g., fixed crystal), the range of the lowest frequency obtainable by crystal substitution or by cavity adjustment through the highest frequency, should be listed. This is true even if only one of several specific crystal frequencies is intended for use. At a later date, it may be necessary to shift the tuned frequency of the equipment, and, by correctly identifying the capabilities of the system, the Army spectrum manager can assess the ability of the system to operate relative to this shift.
If the equipment is designed for use at a single frequency only, cannot be tuned, or in any way adjusted in frequency, the center frequency of the emission or reception should be listed in this block. An example of a fixed frequency system is an ATCRBS IFF/SIF interrogator that would have the entry - "1030 MHz."
If there is more than one transmitter being used to cover the frequency ranges or if the transmitter is capable of tuning over a greater frequency range than is being requested for this allocation, the range listed in this block may differ from the range(s) given on page 1, Item 4, FREQUENCY REQUIREMENTS, Common Errors: Specifying the frequencies planned for use instead of the transmitter range. For example, a software defined radio (SDR) can typically operate over a much wider range of frequencies than will be allowed for its operation.
More About: Software Defined Radio
6. METHOD OF TUNING
Enter the method of tuning and frequency generation device (e.g., crystal, synthesizer or cavity). If the equipment is not readily tunable in the field, indicate the complexity of tuning in the Block 24 REMARKS. Include complexity factors such as skill levels involved, major assemblies involved, time required, and location (factory or depot) where equipment is to be tuned.
This is another two- or three-word descriptor, usually containing information about the method of effecting change and the device that generates the output frequency. Examples are: manually adjusted klystron cavity, fixed crystal, interchangeable crystal, manually adjusted crystal synthesizer, etc. Even if no tuning is possible, the second half of the descriptor is valid. Thus, a non-tunable radar would still have an entry appropriate for this block (e.g., sealed cavity magnetron).
Common Errors: Required information is not supplied.
7. RF CHANNELING CAPABILITY
Describe the radio frequency channeling capability. For uniformly spaced channels, enter the center frequency of the lowest channel, the increments between consecutive center frequencies, and the number of channels (e.g., 406 MHz, 100-kHz increments, 20 channels). For continuous tuning, enter the lowest frequency and the word “continuous.” For nonuniform channelization, or in cases where channel selection is under software control, enter a detailed description in Block 24, REMARKS. Any constraints for using any of these channels must also be described in Block 24, REMARKS (e.g., degraded channels, internal hardwiring limitations, or lockout capability for frequency hopping systems).
The block’s title contains the acronym RF, for radio frequency. This is to qualify that only RF output channeling information is appropriate. Combining multiple input channels through time division multiplexing (TDM) or frequency division multiplexing (FDM) into an RF channel need not be described in this block.
However, multiplexing information should be listed in Block 14, MODULATION TECHNIQUES AND CODING, or Block 24, REMARKS.
Common Errors: The entire frequency band is submitted.
More About: Radio frequency channel, Lockouts
8. EMISSION DESIGNATOR(S)
The emission designator is a string of seven alphanumeric characters that describe both the necessary bandwidth and the emission classification of the signal. Enter the emission designator(s) including the necessary bandwidth for each designator (e.g., 16K0F3E). The method for formulating an emission designator is described in the NTIA Manual of Regulations & Procedures for Federal Radio Frequency Management, included in the Guide. Necessary bandwidth can be determined by following the guidance in Annex J of the NTIA Manual.
For systems with a frequency hopping mode as well as a non-hopping mode, enter the emission designators for each mode as hopping or non-hopping.
Common Errors: Bandwidth indicated in the Emission Designator does not reflect the values supplied in Item 12 EMISSION BANDWIDTH
More About: Emission Designators, Necessary Bandwidth
9. FREQUENCY TOLERANCE
Enter the frequency tolerance (i.e., the maximum departure of a transmitter from its assigned frequency after normal warm-up time has been allowed). Indicate the units in parts per million (ppm) for all emission types except single sideband (SSB), which shall be indicated in Hertz (Hz).
Frequency tolerance is defined as follows:
(MHz)frequencycenter (Hz)driftrtransmittemaximum
(ppm)toleranceFreq =
It should be expressed in parts per million (ppm), rather than actual frequencies or a percentage of the (referenced or assigned) center frequency. A 1-MHz center frequency transmitter that can drift 1 Hz has a frequency tolerance of 1 ppm. A 100-MHz transmitter with a drift of 10 Hz has a tolerance of 0.1 ppm.
Note: The exception is that SSB frequency tolerance may be expressed in Hz.
The tolerance, or drift, of a transmitter from its assigned center frequency is a function of many factors. It may depend on transmitter temperature, age, or center frequency. The value entered should represent the frequency tolerance at the operating temperature and at a time sufficiently into the equipment's life cycle to exclude "Break-in" or "Pre-Burn-In" variations. It is not necessary to list these conditions in Block 9.
Common Errors: The information is not supplied, or does not meet the NTIA frequency drift standards.
More About: Warm-up time, SSB, NTIA Frequency Drift Standards
10. FILTER EMPLOYED
If a filter is employed between the final RF stage and the transmitter antenna, it should be indicated here. Use Block 24, REMARKS, to provide information on the type of filter (e.g., lowpass, highpass, or bandpass) as well as any additional specifications). An example of this additional information would be an entry in Block 24 REMARKS: "Low-Pass filter with 1.5-dB insertion loss and a minimum of 85-dB attenuation 25 MHz removed from the tuned frequency."
Common Errors: Item is marked YES, but the type of filter is not specified.
More About: Filter types
11. SPREAD SPECTRUM
If spread spectrum techniques are being employed, check the YES box and provide a complete description of how the spreading is achieved in Block 14, MODULATION TECHNIQUES AND CODING and Block 24, REMARKS.
Spread spectrum is defined by the Institute of Electrical and Electronic Engineers (IEEE) as "a modulation technique for multiple access or for increasing immunity to noise and interference. Spread spectrum systems make use of sequential noise-like signal structures, for example, pseudonoise (PN) codes, to spread the normally narrowband information signal over a relatively wide band of frequencies. The receiver correlates these signals to retrieve the original information signal." The principal spread spectrum methods are direct-sequence coding, frequency-hopping, or a hybrid of the two. Examples of a REMARKS entry would be "direct-sequence pseudorandom noise code is used to spread the bandwidth of the telecommand signal. Signal information rate = 14.6 kbits/s and chip rate = 18.5 Mbits/s" or "Frequency-hopping is employed using 21 discrete software selected channels within the tuning range. The hop rate is 20 k hops/s."
Common Errors: User selects YES, but does not specify the type of Spread Spectrum.
More About: Spread Spectrum
12. EMISSION BANDWIDTH
This item should contain information regarding the spectral energy distribution of the transmitted signal. The emission bandwidth is defined as the signal appearing at the antenna terminals and includes any significant attenuation contributed by filtering in the output circuit, or transmission lines. The bandwidths of the signals at points -3, -20, and -60 dB, relative to the fundamental signal level, are required, and should not include tuning range or carrier movement. The bandwidth at -40 dB shall also be entered if the transmitter is a pulsed radar transmitter. Values of emission bandwidth specified should be indicated as calculated or measured by marking the appropriate block.
Indicate units used, e.g., Hz, kHz, or MHz. Note that the occupied bandwidth (Block 12.e) is defined as the bandwidth such that, below its lower and above its upper frequency limits, the mean powers radiated are each equal to 0.5% of the total mean power radiated.
During conceptual and experimental stages, the waveform envelope may be calculated. For developmental and operational allocations, measured data should be provided.
The bandwidth of a frequency-hopping signal should be measured at any instantaneous frequency.
This should fall somewhere between the -20 and -40 dB points of the emission bandwidth on most FM systems. Under no circumstances can the occupied bandwidth be less than the necessary bandwidth listed in Block 8, EMISSION
DESIGNATORS(S).
A complete set of bandwidth data must be listed for each different pulse rate, pulse width, pulse rise time, and pulse fall time listed in Block 18, PULSE CHARACTERISTICS. In addition, a complete set of emission bandwidth data must be included for each different emission designator listed in Block 8. For instance, a radar system may be capable of operating as a pulse-Doppler radar or a frequency modulated (FM) chirp radar. In this case, two emission designators would be indicated in Block 8, and correspondingly, two sets of emission bandwidth data must be listed in Block 12. Additional sets of bandwidth data should be put in Block 24, REMARKS, or on continuation pages.
Common Errors: Information is not submitted. An emission designator and bandwidth is not supplied for multiple data rates. The data rates that apply to each emission designator are not provided.
More About: Decibels, Occupied bandwidth
13. MAXIMUM BIT RATE
Enter the maximum information bit rate for digital equipment, in bits per second (bps). If spread spectrum is used, enter the bit rate after encoding. This item ordinarily applies only to digital communication systems. Enter the maximum bit rate, etc., associated with the transmission of information and error correction, in bps. Chip rate information associated with spread-spectrum signals should be provided separately in Block 14, MODULATION TECHNIQUES AND CODING.
Common Errors: Required information is not submitted. Each bit rate should have an emission designator.
More About: Chip rate
14. MODULATION TECHNIQUES AND CODING
Describe, in detail, the modulation and/or coding techniques employed. For complex modulation schemes, such as direct-sequence spread-spectrum, frequency-hopping, frequency-agile, etc., provide full details in Block 24, REMARKS. An example of an entry would be "A 13-bit Barker Code is used to compress the radar pulses."
Common Errors: Information not supplied. More detail, other than that provided by the emission designator is often needed.
More About: Modulation Techniques and Coding
15. MAXIMUM MODULATION FREQUENCY
Enter the maximum modulation, or baseband, frequency. This applies to all analog and digital FM or phase-modulated (PM) signals, and is the maximum 3-dB down point on the high side of the modulating spectrum (i.e., the highest input frequency that is transmitted in that application). For a standard analog voice communications radio, the maximum modulation frequency might be designated as 3 kHz. For multichannel frequency-division multiplexed radio, the maximum modulation frequency is usually the highest frequency of the highest channel after being multiplexed. (In some cases, the pilot tone is placed at the upper end of the modulation envelope. The pilot tone becomes the highest modulating frequency.) For example, if 10 3-kHz channels are multiplexed, the highest modulation frequency is 10 X 3 kHz, or 30 kHz. Indicate the units (e.g., Hz, kHz, or MHz).
For other kinds of systems, the maximum modulation frequency is not needed;
the correct entry is “NA.”
Common Errors: Required information is not supplied.
More About: FM Modulation.
16. PRE-EMPHASIS
This item is applicable only to analog FM systems. Mark the appropriate block to indicate whether pre-emphasis is available. Pre-emphasis refers to preferential amplification of the higher modulating frequencies. Typically, the amplification increase is 6 dB per octave. If the exact amount of pre-emphasis is known, it should be entered in the space provided in the left-hand portion of the block.
Pre-emphasis is common in COTS equipment, but is not generally found in tactical military radios.
Check the NO block for other systems, such as amplitude modulated (AM) and pulse-modulated (PM) systems.
More About: FM Pre-emphasis
17. DEVIATION RATIO
For FM or PM transmitters, enter the deviation ratio computed with the formula:
FrequencyModulationMaximum DeviationFrequencyMaximum
RatioDeviation =
This item applies only to FM or PM equipment. For FM systems, the deviation ratio is the ratio of the maximum amount a one-sided RF emission deviates from the center frequency to the maximum frequency of the input modulating signal.
For FM systems, the deviation ratio is directly proportional to the amplitude of the modulating signal, since the amount of carrier frequency "swing" is tied to the amplitude variance of the modulator. In PM systems, the deviation ratio is tied to both the amplitude of the modulating signal and the phase deviation constant of the modulator.
For example, a deviation ratio of 1 for an FM system indicates that a 3-kHz input frequency will cause a peak instantaneous frequency deviation of 3 kHz. A deviation ratio of 3 is the result of a 9-kHz deviation of the emission when modulated with a 3-kHz signal.
For AM frequency-shift-keying (FSK) systems, the deviation ratio is not applicable.
Enter “NA” in this block for all AM and pulse-modulated systems.
Common Errors: Required information is not supplied.
18. PULSE CHARACTERISTICS
Pulse Characteristics only apply to pulse-modulated systems. Do not enter data concerning short duration FM and AM emission transmitters (e.g., frequency-hopping) in these blocks. Information concerning transmission rates of repetitive
AM or FM emissions should be entered in Block 24, REMARKS, or on a continuation sheet.
Block 18.a. RATE
Pulse rates should be listed for individual pulses. While "pulse pairs" are commonly used in IFF system specifications, it is not correct to list the pulse-pair's repetition rate in this block. Rather, the number of individual pulses per second is the correct figure, and the remarks concerning pulse pairs should be included in Block 14, MODULATION TECHNIQUES AND CODING, or Block 24, REMARKS.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .