N00421-17-Q-0010.docx

DOCX document 94 KB Posted

Attached to
Data Acquisition System Federal contract opportunity
Solicitation number
N00421-17-Q-0010
Issued by
Department of the Navy Naval Air Systems Command Naval Air Warfare Center

View the file

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

N0042117Q0010

Section A - Solicitation/Contract Form

SOLICITATION/CONTRACT FORM

Solicitation N00421-17-Q-0010 is issued as a competitive procurement. The Government intends to purchase on a firm fixed-price basis, and to solicit and negotiate the proposed purchase order on a competitive basis for Data Acquisition System in accordance with the specifications provided in section C.

OFFERS MUST BE TAA COMPLIANT.

ALTHOUGH NOT SET-ASIDE FOR SMALL BUSINESS; “REASONABLE” OFFERS FROM SMALL BUSINESS OWNERS WILL BE THE PRIORITY FOR CONSIDERATION.

***Basis for Award***

ACCEPTING OFFER’S FROM AUTHORIZED DISTRIBUTORS/RESELLERS ONLY

Solicitation closing date/time is firm; proposals received after the deadline will not be accepted. Your quote must contain enough technical information i.e. data sheet, drawing, specification, etc. for evaluation. Your quote will only be evaluated based on the information provided. The award will be made on the basis of lowest evaluated price of proposals meeting or exceeding the acceptability standards for non-cost factor. This is a firm fixed-price procurement; therefore, the initial offer should represent the vendor’s best quote in terms of price and technical acceptability. A determination by the Government not to accept the proposal for not meeting the minimum requirement is solely within the discretion of the Government.

Interested parties must be registered in System for Award Management (SAM) Database prior to submission of an offer to be considered for award of any Department of Defense contract. This can be accomplished electronically at http://www.sam.gov/vendor.cfm. The Government will not pay for any information received

Government Point of Contact:

Bernie Cortez Naval Air Warfare Center AD (PAX)

2.5.1 RAC, 21983 Bundy Road, BLDG 441

Patuxent River, MD 20670-1127 Email: bernie.cortez@navy.mil (preferred method).

Section B - Supplies or Services and Prices

ITEM NO
SUPPLIES/SERVICES
QUANTITY
UNIT
UNIT PRICE
AMOUNT
1
Each

Data Acquisition System

FFP

The requirment is for a High Performance Data Acquisition ( DAQ ) and display system to allow the operator to safely run and acquire data from the test article. This system will allow us to acquire critical data to help NAVAIR to meet all future testing requirements. INTERESTED PARTIES SHALL SUBMIT THEIR PROPOSAL IN ACCORDANCE WITH THE SPEC LISTED IN SECTION C.

**YOUR PROPOSAL MUST CONTAIN ENOUGH TECHNICAL INFORMATION I.E. DATA SHEET, DRAWINGS, SPECIFICATION, ETC. TO BE EVALUATED. LINE ITEMS MUST BE BROKEN DOWN AND PRICED SEPERATELY AS YOU SEE FIT. THIS IS A FIRM FIXED PRICE PROCUREMENT. AWARD WILL BE MADE ON THE BASIS OF LOWEST PRICE TECHNICALLY ACCEPTABLE. ALTHOUGH NOT SET-ASIDE FOR SMALL BUSINESS; "REASONABLE " OFFERS FROM SMALL BUSINESS OWNERS WILL BE THE PRIORITY FOR CONSIDERATION**.

Hardware must be delivered by May 31st 2017. Scramnet / Data Acquisition Software must be delivered by July 31st 2017. Government will provide Scramnet Hardware Card and assist in answering vendors questions to aid in implementation with vendor software.

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

FOB: Destination

NET AMT

Section C - Descriptions and Specifications

SPECIFICATIONS

NAVAL AIR SYSTEMS COMMAND 4.4.6.5

PROPULSIONS SYSTEMS EVALUATION FACILITY

Technical Requirements for Propulsions Systems Evaluation Facility (PSEF) Data Acquisition System for T700 Test Cell Room#122

DAA/MHJ

2/6/2017

Project Description and Scope ..…………………………………………………………01
Codes and Standards …………………………………………………………………….01
General Information ……………………………………………………………………..02
Facility Description ………………………………………………………………………02

Party Definitions ……………………………………………………………………… 02

Owner Project Contacts ………………………………………………………………….02
Definitions ………………………………………………………………………………...03
General Requirements …………………………………………………………………...05
Project Contact/ Coordinator …………………………………………………..05
Engineering ……………………………………………………………………….06
Environmental ……………………………………………………………………06
Power ……………………………………………………………………………...07
Data Collection and Monitoring ………………………………………………..07
Data Interfaces (Digital Communication)……………………………………...08
DC Analog ………………………………………………………………………..08
Thermocouples …………………………………………………………………...10
RTD’s ……………………………………………………………………………...10
Low Level Inputs ………………………………………………………………...10
Strain Gauges …………………………………………………………………….10
Speed Probe Measurements ……………………………………………………10
Discrete Inputs …………………………………………………………………...11
Discrete Outputs …………………………………………………………………11
Processing and Program ………………………………………………………...11
Display and Trending …………………………………………………………...12
User Interfaces ……………………………………………………………………13
IT and Enterprise Connectivity …………………………………………………14
Serviceability……………………………………………………………………...15
Life Cycle and Warranty ………………………………………………………………...15
Vendor Exceptions……………………………………………………………………….16
Training……………………………………………………………………………………16
Schedule…………………………………………………………………………………...16
Documentation Requirements……………………………………..……………………16

Technical Scope of First System to be Proposed – T700 Room # 122……………… .17

Main Operational Performance Subset…………………………………………………18
Bidders Proposal Requirements…………………………………………………………19
Scope of Work – Cost Breakout Sheet ………………………………………………….20

Page tc

1. Project Description and Scope:

1.1. This specification covers the design, integration, testing, and delivery FOB destination, of a complete Data Acquisition System as described henceforth.

1.2. This specification is a full performance and functional description of the Data Acquisition System. It does not mandate every particular technology, or implementation definition. It does define the system performance and functional requirements necessary to ensure the following:

1.2.1. Delivery of an open, interoperable system.

1.2.2. Delivery of a fully serviceable system where the owner “owns” the system.

1.2.3. Delivery of a system with full functionality and performance with incorporated system security requirements as defined by Owner’s Information Technology (IT) department.

1.2.4. Inhibits vendor closed proprietary system elements.

1.2.5. Ensures the Data Acquisition Supplier delivers a working system in which the owner/ purchaser has all of the training, software, and tools to perform their own test set-up, and data analysis as well as maintenance, upgrades, and service.

1.2.6. Provides for competitive bidding on the initial installation of the system as well as future service contracts.

2. Codes and Standards:

2.1. All Alternating Current (AC) power and grounding shall comply with the national Electrical Code (NEC).

2.2. Calibrations for proof of required specified limitations shall be documented and traceable to the National Institute of Standards and Technology (NIST).

2.3. International Protection Marking, IP Code, published by International Electrotechnical Commission (IEC) 60529; IP 65/ IP67.

2.4. Precision Time Protocol version2 (PTPv2) Institute of Electrical and Electronic Engineers (IEEE) 1588-2008

2.5. Transducer Electronic Data Sheet (TEDS) IEEE 1451.4

2.6. Aeronautical Radio INC. (ARINC) - ARINC 429 technical standard.

3. General Information:

3.1. Facility Location

3.1.1. Patuxent River Naval Air Station

Propulsion Systems Evaluation Facility 4.4.6.5 Building # 2360

3.2. Mail Address:

3.2.1. Naval Air System Command 4.4.6.5

Propulsion Systems Evaluation Facility 22229 Elmer Road BLDG 2360 Patuxent River, MD 20670

4. Facility Description

4.1. PSEF is a facility owned and utilized by the United States Navy for various system, sub-system, and component testing, primarily, but not limited to fleet aircraft. Test articles include Navy, Marines, Air Force, Army as well as a variety of Commercial entities systems. In performing such tests data is collected and analyzed for determining performance, life cycle, and failure cause modes. The quality of the collected data is of the upmost importance such that model development and analysis provide accurate findings.

5. Party Definitions:

5.1. Owner: Department of the Navy, Naval Air Systems Command 4.4.6.5

5.1.1. Propulsions Systems Evaluation Facility (PSEF)

5.2. Vendor: The successful company who is awarded the contract, and who has accepted the Owner’s term and conditions.

5.3. Bidder: Those companies submitting bids for fulfilling the requirements of this project.

6. Owner Project Contacts:

6.1. XXXXXXXXXXXXXXXXXXXXXXX

XXXXXXXXXXXXXXXXXXXXXXXXXX

6.2. Technical Requirements Engineer: XXXXXXXXXXXXXXXXXXXX

Email: XXXXXXXXXXXXXXXXXXXXXXXX

7. Definitions:

7.1. Alarm: Notification of an abnormal condition.

7.2. Algorithm: A logical procedure for solving a recurrent mathematical problem.

7.3. Alternating Current (AC): Voltage in which the charge carriers in a conductor or semiconductor periodically reverse their direction of movement at a relative pre-defined period.

7.4. Analog: Continuous signal of data. In the case of this requirement a continuous signal of data measurement, or data output.

7.5. Analog to Digital Conversion (A to D, A-D): Method of measuring continuous signal in time and converting value into a digital measurement form.

7.6. ARINC 429: Aeronautical Radio INC. (ARINC) is the technical standard for the predominant avionics data bus used on most higher-end commercial and transport aircraft. It defines the physical and electrical interfaces of a two-wire data bus and a data protocol to support an aircraft's avionics local area network.

7.7. Binary: A two-state measurement and/ or computational system information is represented by on/ off, true/ false, or 0/ 1 etc.

7.8. Common Mode Rejection Ratio (CMRR): Rating of common mode noise rejection ratio; |Adm/Acm|, where Adm is gain differential mode, and Acm is gain common mode. Described in decibels (Db) as Db=20log10(Adm/Acm).

7.9. Compact Disk (CD): Optical digital storage medium in shape as a disc.

7.10. Data Acquisition System: DAS or DAQ, A system comprised of the necessary components for the capturing of analog and/ or discrete information from physical test articles. Information is inputted into the DAS in the form (in any combination) of analog electrical, discrete electrical, and electronic frequency. For the purposes of this specification the DAS will be of a digital computer type – digitizing, presenting and saving all inputted information as collected.

7.11. Decibel (Db): a logarithmic unit used to express the ratio of two values. In the case of this specification Db is the ratio of voltage amplitude as expressed as Db=20log10(V1/V2).

7.12. Digital: A quantized measurement or output of a signal at a specific moment in time.

7.13. Discrete: A signal input or output usually utilized for on/ off control, or detection of on/ off (open/ close) action.

7.14. Direct Current (DC): Voltage in which the charge carriers in a conductor or semiconductor flow in one continuous direction.

7.15. Digital Versatile Disc (DVD): Optical digital storage medium with higher storage capability as compared to a CD.

7.16. Fast Fourier Transform (FFT). An algorithm which computes the discrete Fourier Transform (DFT) of a sequence. For the purpose of this specification, converts a signal from its original domain (time) to a representation in the frequency domain.

7.17. Graphical User Interface (GUI): A monitor, visual subset of operator interfaces.

7.18. Ground: An electrical connection to earth. Purpose is for electrical safety, and for instrument measurement reference.

7.19. Human Machine Interface (HMI),(GUI – Graphical User Interface): A graphical, object-oriented method by which an operator is capable of communicating with the system. The Human-Machine interface allows the operator to manage, control, monitor, and configure the system.

7.20. Hysteresis: The phenomenon in which a measurement, or final element position lags, or does not respond to, a change in the measured media or position demand, and is influenced by the previous measurement, or movement of the device.

7.21. Initialization for Integrated Electronics Piezoelectric (IEPE): A class of transducer (acceleration). Utilizes a built-in voltage amplifier in conjunction with two conductor wiring carrying constant excitation current for power, and voltage for measurement.

7.22. Input/ Output (I/O): Designation for measured inputs and driven outputs of: analog voltage, current, discrete forms.

7.23. Inter-Range Instrumentation Group time codes (IRIG): Standard formats for transferring timing information.

7.24. IP Code: International Protection Marking, IEC standard 60529, classifies and rates the degree of protection provided against dust, and water, etc.

7.25. Linearity: The measure of the extent to which a certain response is directly proportional to the applied measured media changes. This applies to an input measurement, and to demand changes to a final element.

7.26. MODBUS: Serial communications protocol originally published by Modicon in 1979 for use with its programmable logic controllers (PLC). Utilizes American Standard Code for Information Interchange (ASCII) or Remote Terminal Unit (RTU) modes. Serial communication to only one device is by Recommended Standard (RS-232). Serial communication to multiple devices is by RS-485. Ethernet communication is also available with Transmission Control Protocol (TCP).

7.27. Operating System (OS): Software which controls the execution of computer programs.

7.28. Operator Interface: A device combination of hardware and software, personal computer (PC), workstation, laptop or display terminal, which provides client access to the Data Acquisition System. Can be used for: configuration, network management, diagnostics, data manipulation, data analysis etc. in real time or in displaying previously collected data.

7.29. Peripheral: External devices used for communication to and from a computer. Peripherals include CRT, printer, hard drives, disk drives, modems, etc.

7.30. Precision Time Protocol (PTP): A protocol utilized to synchronize clocks on multiple computers or data collection modules.

7.31. Sensor: Device capable of measuring the condition or value of a physical variable including but not limited to: magnetic, electromagnetic, electrical, pressure, temperature etc.

7.32. Skew error: The error from the collection of multiple data point channels in which the time reference of a single channel as presented or later reproduced is not reflective of the actual time of digitization. Skew is the time delta between the actual and presented (or reproduced) signal in relation to actual time, or another channel simultaneously collected.

7.33. Software: Programs and routines used to extend the capabilities of computers hardware.

7.34. Transducer Electronic Data Sheet (TEDS): Standardized method of storing transducer (sensors or actuators) identification, calibration, correction data, and manufacturer-related information.

7.35. Time Synchronization: Algorithm to assure multiple data points from multiple various locations are time stamped from a central clock, and the data points are actually digitized at the clock time stamp indicated.

7.36. Transducer: A device that converts one form of energy into another form. For the case of this specification, a device that converts variations in a physical quantity into an electrical signal.

7.37. Transmitter: A device that measures a physical process and converts to an electrical signal that is amplified, and capable of scaled calibration. A transmitter may utilize a transducer, varying capacitance, etc. for the primary measurement before amplification.

8. General Requirements:

8.1. The Vendor shall include at a minimum:

8.1.1. Project Contact/ Coordinator:

8.1.1.1. Vender shall include a single point of contact in reference to project technical, interfacing, installation questions and discussions.

8.1.1.1.1. Project Contact may reference, and refer to various subject matter experts in regards to detailed and highly technical type discussions.

8.1.2. Engineering:

8.1.2.1. Vendor to supply a complete Engineered System ready for installation, connection to instrumentation, and data acquisition for buyer general test purposes.

8.1.2.2. Vendor to supply complete engineering drawings of system internal connections, network connections, and instrumentation connections. Connector shall be ODU Lemo Type along with Mini T/C connections.

8.1.2.3. Vender shall supply complete installation instructions and recommendations:

8.1.2.3.1. Instructions shall include mechanical frame work needs, grounding requirements, shielding recommendations at a minimum.

8.1.2.4. Vendor shall supply complete operator and test engineering instructions:

8.1.2.4.1. Instruction shall include all channel signal connections, all channel signal set-up, all trending tools, all display tools, all historizing tools, all analysis tool usage, etc.

8.1.3. Environmental:

8.1.3.1. System shall be environmentally hardened.

8.1.3.1.1. System shall have capability for installation in enclosed rooms and chambers that are not air-conditioned, or heated, and subject to the influence of outdoor temperature and humidity.

8.1.3.1.1.1. I/O portion of system shall be capable of total system functions installed in a chamber/ room; have no degradation of stated performance, and no reduction of warranty in the following states:

8.1.3.1.1.1.1.1. Operating.

8.1.3.1.1.1.1.2. Powered on, standby.

8.1.3.1.1.1.1.3. Power off, open storage.

8.1.3.1.1.1.1.3.1. For all above states:

8.1.3.1.1.1.1.3.2. Withstand Temperature between (-) 20 degree F. to (+) 150 degree F.

8.1.3.1.1.1.1.3.3. Withstand Humidity 100% condensing, and be water tight. (Meet IP65/ IP67)

8.1.3.1.1.1.1.3.4. Be Dust tight. (Meet IP65/ IP67)

8.1.3.1.1.1.1.3.5. Withstand Vibration up to 5g.

8.1.3.1.1.1.1.3.6. Withstand Shock up to 50 g.

8.1.4. Power:

8.1.4.1. System shall utilize two (2) independent AC power inputs, such that a single AC power feed failure does not disrupt data collection, or system operation. AC power @ 120VAC to be supplied by the buyer. Vendor shall provide AC current, and AC power quality needs.

8.1.5. Data Collection and Monitoring:

8.1.5.1. Data Collection Platform, (not inclusive of operator/ engineer workstation), shall incorporate a real-time, deterministic operating system.

8.1.5.1.1. Operating System shall be fully licensed, with full rights conveyed to buyer.

8.1.5.1.2. Vendor shall supply information of time latency for data digitization, with guaranteed performance.

8.1.5.2. Vendor shall supply initial system with capability to perform rate of collection (Samples per second) that is user selectable up to a maximum rate of at least 40K samples/ second.

8.1.5.2.1. Note: Sample rate specifics for individual type signals are listed in related document sections.

8.1.5.3. Vendor shall supply system with future capability to perform rate of collection (Samples per second) that is user selectable to a maximum rate of at least 200K samples/ second.

8.1.5.4. Typical Analog to Digital conversion shall be at 16 bit resolution.

8.1.5.4.1. Analog Inputs measurement electronics shall have sensitivity equal to or greater than the bit conversion resolution for lowest stated DC value capability.

8.1.5.4.2. System overall (combined) uncertainty (accuracy) shall be less than or equal to 0.10%

8.1.5.5. Data History shall be capable of a minimum of two (2) hours storage for 300 inputs collecting at the maximum speed of 1K samples/ second.

8.1.5.6. There shall be no data skew channel-to-channel, of any collected channels.

8.1.5.7. All data collected channels shall be time stamped, at time of collection.

8.1.5.8. All data channels shall be readily trended and/ or displayed in real time (Time Domain).

8.1.5.9. Display of multiple data channels in the time domain shall not have any time error, or time delta between any channels trended simultaneously (That is, no display skew).

8.1.5.10. All history data shall be readily trended and/ or displayed in the time domain.

8.1.5.11. Vendor shall supply system capable of time synchronization and adjustment from external source:

8.1.5.11.1. IRIG is minimally acceptable time synchronization from external source.

8.1.5.11.2. System shall have module-to-module time synchronization such as Precision Time Protocol version2 (PTPv2).

8.1.5.12. Vendor shall supply system compatible and capable of interfacing with TEDS instrumentation.

8.1.6. Data Interfaces (Digital Communication):

8.1.6.1. MODBUS Interface:

8.1.6.1.1. System shall be capable of connectivity, communicating and incorporating values through a serial MODBUS interface via RS-232, RS-485 or Ethernet TCP.

8.1.6.1.2. RS-485 shall be capable of communication with 32 devices (drops).

8.1.6.2. LabVIEW Interface:

8.1.6.3. System shall be capable of connectivity, communicating and incorporating values with National Instruments LabVIEW systems.

8.1.6.4. SCRAM Net:

8.1.6.5. System shall be capable of connectivity, communicating and incorporating values through SCRAM Net systems.

8.1.7. DC Analog: Up to (+)/(-) 60 VDC

8.1.7.1. DC Analog Voltage inputs shall be of a deferential type with minimal 100 Db CMRR (DC) and a minimal 95 Db CMRR at 60 Hz.

8.1.7.2. Analog inputs shall have capability for user selectable filtering including: Butterworth, Bessel, Normal RC.

8.1.7.2.1. Filters shall have user adjustable settings:

8.1.7.2.1.1. Filter order.

8.1.7.2.1.2. 3Db cutoff frequency.

8.1.7.2.1.3. Filters shall have ability to be low pass, high pass or band pass configured.

8.1.7.3. Analog inputs shall be isolated channel-to-channel and channel-to-ground.

8.1.7.3.1. Analog inputs shall be fully galvanic isolated.

8.1.7.3.1.1. Galvanic isolation shall be 50 Volts minimum.

8.1.7.3.1.2. System shall have capability to have (+)/(-) 50 VDC applied continuously without damage.

8.1.7.3.1.3. System shall have capability to have 100 VAC peak-to-peak ( 35.35 VACrms) continuously without damage.

8.1.7.4. Analog inputs measurement shall be scalable from -10 to + 10 VDC.

8.1.7.4.1. Measurement capability of system shall be the full scalable range (-)10.0000000 to (+)10.0000000 VDC minimum.

8.1.7.5. Analog voltage inputs shall have a minimum input impedance of 1 Megaohm.

8.1.7.6. Analog current input shall have a maximum input impedance of 25 Ohm.

8.1.7.7. System shall have ability to supply excitation voltage with full current capability for all analog input channels for customer utilization of two wire transducers and transmitters.

8.1.7.7.1.1. Excitation capability shall not prohibit analog inputs from measurement of voltages from self-powered, or externally excited transducers and transmitters.

8.1.7.7.1.2. System shall have capability to mix usage, at any ratio, both system exited and externally exited transducers and transmitters.

8.1.7.8. Analog DC inputs collection rate shall be user settable up to 20,000 samples per second.

8.1.7.9. Analog DC outputs update rate shall be user settable up to 20,000 updates per second.

8.1.7.9.1. Direct analog out from input signal is acceptable.

8.1.7.9.2. Output error shall be less than or equal 0.04% @ +/- 10VDC.

8.1.7.10. Analog DC Voltage outputs shall have the capability of providing (-) 10 to (+) 10 volts, driving a minimum load impedance of 250 ohms.

8.1.7.11. Analog DC Current output shall have the capability of driving zero to 20 milliamperes, and 4 to 20 milliamperes, into a maximum load of 1000 Ohms.

8.1.8. Thermocouples:

8.1.8.1. System shall have ability for measuring all standard thermocouples (type K, J, T, E etc.) with cold temperature compensation and linearization techniques independent of need for user adjustment.

8.1.8.2. Thermocouple measurement shall provide user selectable low pass input filtering.

8.1.8.3. Thermocouple measurement rate of collection shall be capable of up to 600 samples per second.

8.1.9. RTD’s:

8.1.9.1. System shall have ability, at a minimum, to measure 100 Ohm Platinum Restive Temperature Device (RTD) primary elements.

8.1.9.2. RTD measurement shall provide user selectable low pass input filtering.

8.1.9.3. RTD measurement rate of collection shall be capable of up to 600 samples per second.

8.1.10. Low Level Inputs:

8.1.10.1. System shall have ability to measure low level voltage inputs from standard type transducers.

8.1.10.2. Low level transducer measurement rate of collection shall be capable of 20,000 samples per second.

8.1.11. Strain Gauges:

8.1.11.1. System shall have ability for static and dynamic strain gauge measurement.

8.1.11.2. System shall have ability to provide a constant current excitation of strain gauges utilizing a four (4) wire method.

8.1.11.3. Strain gauge measurement rate of collection shall be capable of 40, 000 samples per second.

8.1.12. Speed Probe Measurements:

8.1.12.1. System shall have the capability of speed signal detection from all standard speed probes including magnetic variable reluctance/ inductive, Hall Effect, and external test pulse train source.

8.1.12.2. System shall have the ability for speed calculation updating at a rate of 20 times per second.

8.1.12.2.1. System shall have the ability for Engineering and Operator input constants for speed calculations (such as teeth on wheel).

8.1.12.3. System shall have automatic trigger threshold, and hysteresis adjustment.

8.1.12.4. System shall have ability for acceleration calculation.

8.1.12.5. System shall have ability to measure frequency and amplitude from displacement type transducer or transmitter.

8.1.13. Discrete Inputs:

8.1.13.1. System shall have capability of detecting discrete input measurement to include:

8.1.13.2. Relay contact detection.

8.1.13.2.1. System shall have ability to supply excitation “wetting” voltage.

8.1.13.3. Voltage detection:

8.1.13.3.1. System shall have ability to detect voltage level and set as logic Boolean data.

8.1.14. Discrete Outputs:

8.1.14.1. System shall have ability to provide discrete output.

8.1.14.2. Discrete outputs shall include externally sourced voltage “dry” contact type.

8.1.14.2.1. Dry contact shall include DC and AC capability.

8.1.14.2.2. DC dry contact types may be electro-mechanical or solid state rated at 32 VDC at 1 ampere.

8.1.14.2.3. AC dry contact type shall have ability for 120 VAC at 1 ampere.

8.1.14.3. Discrete outputs shall include system powered, voltage supplied type.

8.1.14.3.1. System powered type shall supply 24 VDC, with capability of 20 milliamps.

8.1.15. Processing and Program:

8.1.15.1. Processing system shall have the ability to be fault tolerant or redundant such that a single processor failure will not stop data collection.

8.1.15.2. Processing system shall allow for replacement of a fault tolerant or redundant processor without interrupting data collection.

8.1.15.3. System shall continuously monitor status and health of all major components and provide alarming upon detection of any failure.

8.1.15.4. Vendor shall supply system fully programmable by the buyer.

8.1.15.4.1. Programmable devices shall be programmed with an available and supplied programming tool.

8.1.15.4.2. Device programming tools shall be fully licensed and conveyed at contract sign off.

8.1.15.5. Programmable devices shall follow open standard interoperability guidelines. No closed or proprietary interfaces to programmable devices shall be allowed.

8.1.15.6. Once programmed a programmable device shall interoperate as any other application specific device on the system network. No closed or proprietary communication to programmable devices shall be allowed.

8.1.15.7. Field programmability of devices shall be provided.

8.1.15.8. Device programming tools shall be able to run on the Operator Workstation.

8.1.15.9. Programming tools shall include ability to access all DAS data in “real-time” and perform:

8.1.15.9.1. Math (algebraic equation capability).

8.1.15.9.2. Boolean functions allowing utilization and interfacing all Boolean logic gates (and, or, nand, nor, flip flop, flip flop –reset dominant, timing/ clock, etc.)

8.1.15.9.3. Programming scripting (shell scripting, assembly language, C).

8.1.15.9.4. Programming shall include “higher” pre-defined function blocks such as: median select, averaging, low value select, high value select etc.

8.1.16. Display and Trending:

8.1.16.1. System shall provide user settable analog value (numbers), and Boolean digital screen displays.

8.1.16.2. System shall have ability for multiple process trending:

8.1.16.2.1. Trending package shall include user settable X-axis delta, that “slides” with time (X-axis time delta remains the same, but provides continuous time trending).

8.1.16.2.2. Trending package shall have user settable Y-axis delta that “slides” (Y-axis amplitude delta remains the same, but provides continues trend view as value increases above original maximum, or decreases below original minimum).

8.1.16.2.3. Trending package shall have capability for multiple traces simultaneously (minimum of 4 traces).

8.1.16.3. System shall have capability of providing Fast Fourier Transform (FFT) frequency domain displays.

8.1.16.3.1. FFT displays shall be available in “real” time, during signal measurement, and from stored history measurement.

8.1.16.3.2. FFT display shall allow user selectable windowing including:

8.1.16.3.2.1. Flat Top, Rectangular, Hann, Hamming.

8.1.17. User Interfaces:

8.1.17.1. Vendor shall supply user Interfaces (software – we may supply hardware):

8.1.17.2. Vendor shall supply a system with multiple levels of user security:

8.1.17.2.1. Vendor shall supply Administration, Engineering, Operator, and Technician sign-on/ password levels of security at a minimum.

8.1.17.2.2. Vendor shall supply a system with multiple individual sign-on for each level described above.

8.1.17.2.3. Vendor shall supply a system with automatic logging of user sign-on and time.

8.1.17.2.4. Vendor shall supply a system with automatic change tracking: logging test and system changes, including user, date and time.

8.1.17.3. Vendor may provide an engineer/ operator workstation. [Possibility that we supply our own, ask vendor for minimum requirements….]

8.1.17.3.1. Vendor shall include listing of manufacturer, model, type, operating system and drawings for interconnection to any supplied PC.

8.1.17.3.2. The operator workstation shall have the ability to monitor, control, diagnose, and display all data which are indicated as: Monitored, Controlled, Displayed, Trended, Alarmed, Override, or Reported.

8.1.17.3.3. An operator software package shall provide the ability to monitor, control, trend, alarm, and override data points.

8.1.17.4. All host computer software shall be fully licensed. Software shall include original Optical Media (CD and/ or DVD) of each application. All applications shall be property of the project owner. All software keys, licenses, dongles, etc. shall be conveyed at contract sign-off.

8.1.17.5. Host software shall not have a closed (non-open) interface to any hardware. No explicitly addressed communication will be allowed. All communication to devices shall follow industry open standards. No vendor lock-in will be allowed.

8.1.17.6. The vendor shall prove and verify that all host software to hardware communication is open and interoperable to the satisfaction of the owner/engineer.

8.1.18. IT and Enterprise Connectivity:

8.1.18.1. The control network shall interface and connect to the data network using industry standard interfaces. TCP /IP Base network using IPv4 and IPv6. Microsoft Windows Server based.

8.1.18.2. No proprietary closed interfaces will be allowed.

8.1.18.3. Contractor shall interface with owners IT department to define any and all IT needs for this system. Contractor shall abide by all decisions and requirements of the IT Department.

8.1.18.4. Basic IT requirements: All new software must be compatible with Microsoft Windows 10 Enterprise Edition 64 bit.

8.1.18.4.1. Devices in hardware and software shall prevent intra-network communication problems.

8.1.18.4.2. All complex devices shall be delivered with a device software configuration plugin capable of being run from any standard network management tool. No proprietary configuration communication mechanisms will be allowed. Software shall be non-volatile.

8.1.18.4.3. All devices shall be capable of identifying themselves via a visual indicator if requested to by a network management or commissioning tool.

8.1.18.4.4. All devices configuration and applications shall be able to be updated over the network. In no cases shall a device have to be physically removed from the network in order to be updated with new software or configuration.

8.1.18.4.5. Workstations are “locked down” using Security Technical Implementation Guides. (STIGS)

8.1.18.4.6. Connectivity to the enterprise network shall ensure data integrity, reliability, performance, and security. Contractor to interface with owner’s enterprise, and IT personnel to ensure system functionality.

8.1.19. Serviceability:

8.1.19.1. Vendor shall deliver a fully functioning, complete, serviceable system.

8.1.19.1.1. All devices shall be fully programmed when commissioned.

8.1.19.1.2. All systems and subsystems shall be demonstrated to be fully operational.

8.1.19.2. Vendor shall provide a system with complete access to all modules and components. All elements of the system must be accessible by owner maintenance staff.

8.1.19.3. Vendor shall supply list of recommended spare parts.

8.1.19.4. Vendor shall include a recommended maintenance need for supplied system including all components.

8.1.19.5. Vendor shall supply calibration methods, traceability, and standards utilized for Owner’s Technical requirements for delivered system.

8.1.19.6. No contractor or vendor proprietary service tools shall be allowed.

8.1.19.6.1. All service tools shall be included as part of the delivered system.

8.2. Life Cycle and Warranty:

8.2.1. Vendor shall include statement of Life Cycle of proposed technology/ solution including proposed technology/ solution maturity and guaranteed future support commitment.

8.2.2. Supplier shall provide a buyer optional service contract costing for 3 years after the end of the warranty as a separate cost. Service contract costs must be defined as an annual cost for full servicing including future software upgrades. This cost shall be defined as an annual cost for years 1, 2 and 3 separate from the initial installation bid.

8.2.3. Vendor shall provide a full and complete system warranty for a service period of five (5) years commencing after final delivery. Bidder to supply detail of guarantee proposal.

8.2.3.1. The warranty shall provide full system functionality, parts replacement, labor, software, and hardware upgrades necessary in to ensure full system functionality during the warranty period.

9. Vendor Exceptions:

9.1.1. Vendor shall, and is expected to, identify exceptions to any provisions within this specification, and provide detail explanation for supporting the provision.

9.1.2. This specification does not purport to be entirely exhaustive of all possible solutions or methods. It is therefore burdened on the vendor to utilize proper engineering expertise and experience for any alternative approaches. Judgment, evaluation, and approval of such approaches rest solely upon the buyer.

10. Training:

10.1. Training shall be provided on the full operation of the DAS.

10.2. Training shall be provided for all network management, commissioning tools, and network diagnostic and analysis tools.

10.3. Training shall be provided on the system architecture, basic protocol capabilities, and servicing of the system.

10.4. Training shall be provided on all device configuration and programming tools.

11. Schedule:

11.1. Vender shall provide schedule for assembly, factory testing, factory calibration, and delivery from time of contract award to delivery of system.

11.1.1. The projected schedule will be consistent with PSEF internal needs. Buyer retains the right to change the schedule up to contract award.

12. Documentation Requirements:

12.1. Vendor shall supply three (3) completes sets of paper (11” x 17”) drawings, and electronic drawings (CD or DVD) in AutoCAD to include:

12.1.1. Mechanical layout and physical dimensions of completed Data Acquisition System.

12.1.2. Physical Block Diagram to include layouts, single line diagrams of internal (related to internal system) connections.

12.1.3. Functional Block Diagram of System (Controller/ Processor, I/O modules etc.)

12.1.4. I/O connection diagrams.

12.2. Vendor shall supply three (3) completes sets of printed manuals, and electronic manuals in Word to include:

12.2.1. Installation detail instruction manuals.

12.2.2. Test set-up, Operators detail instruction manuals.

13. Technical Scope of System to be Proposed – T700 Test Cell (Room#122)

13.1.1. Delivered Data Acquisition System shall have the capability of digitizing, collecting, displaying the following inputs:

13.1.1.1.1. 16 Analog Inputs (+/- 10 VDC)

13.1.1.1.2. 4 Frequency Inputs

13.1.1.1.3. 16 Type J Thermocouple

13.1.1.1.4. 8 Type E Thermocouple

13.1.1.1.5. 16 Type K Thermocouple

13.1.1.1.6. 4 Magnetic Speed Probe Inputs

13.1.1.1.7. 2 Discrete Outputs

13.1.1.1.8. 3 Discrete Inputs

13.1.1.1.9. 4 Accelerometer (Vibration) IEPE/ICP Transducer Inputs

13.1.1.1.10. RS-485 MODBUS interface with ability to communicate with up to a 32 devices (standard).

13.1.1.1.11. National Instruments LabVIEW interface with full communication ability.

13.1.1.1.12. SCRAM Net interface with full communication ability.

14. Main Operational Performance Parameter Subset.

Parameter DescriptionMeasurementThreshold RatingTarget Rating
Environmental:

Temperature:

Humidity (Water tight) Dust tight Vibration Shock

Storage, standby, run:

Temperature Water Tightness Dust Tightness Vibration Resistance Shock Resistance Capability:

(-) 20 to (+) 150 degree F Meet IP65/ IP67 Meet IP65/ IP67 Withstand 5g Withstand 50g Capability:

(-) 40 to (+) 176 degree F n/a n/a Withstand 10g Withstand 75g

Power
Redundant source availability
Redundant source capable
Redundant source capability supplied
Data Collection and Monitoring – Operating System
Operating System (data collection, independent of engineer/ operator workstation)
Robust, minimal interruption of data collection proven operating system.
True real-time (deterministic) operating system.
Data Collection and Monitoring – A to D resolution
Analog to Digital conversion resolution
16 bit resolution
24 bit resolution
DC Analog - CMRR
Common Mode Rejection Ratio (CMRR)
100 dB (DC)

95 dB (AC @ 60 Hz) 125 dB (DC) 100 dB (ac @ 60 Hz)

DC Analog – Linearity Error %

@ +/- 10VDC

Linearity Full Scale
.05
.03

DC Analog – Accuracy %

@ +/- 10VDC

Accuracy Class
.05
.03
DC Analog - Galvanic Isolation
Voltage limit
50 Volts DC
300 Volts DC

15. Bidders Proposal Requirements:

15.1. Bidder shall make known:

15.1.1. Schedule:

15.1.1.1. Time to delivery after contract award.

15.1.2. Supply Power Requirements.

15.1.3. Grounding Requirements.

15.1.4. Physical requirements:

15.1.4.1. Dimensional size.

15.1.4.2. Weight of system (including all components).

15.1.4.3. Environmental limits:

15.1.4.3.1. Temperature, Humidity, Shock, Vibration ratings.

15.1.5. Provide System Design Description including:

15.1.5.1. Systems, sub-systems, modules, cards, etc.

15.1.5.2. Method of A-D (Delta-Sigma, Integration, Successive Approximation, etc.)

15.1.5.3. CMMR.

15.1.5.4. Filter(s) capability with description and performance statement/ plot.

15.1.6. Provide System Security Description including:

15.1.6.1. Multiple user sign on methods.

15.1.6.2. Change Tracking.

15.1.6.3. Owner IT required security.

15.1.7. Statement of life cycle.

15.1.8. Statement of warranty.

15.1.9. Statement of support.

15.1.10. Statement of full compliance with specification, and/ or listing of vender exceptions with alternative details.

15.1.11. System configuration description and examples.

15.1.12. Recommended training (duration, maximum student count).

15.1.13. Proposal as per attached cost breakdown sheet.

Scope of Work - Cost Breakout Sheet Vendor shall supply all material, software, configuration and documentation to deliver a fully operational system as described in this specification:

Bidder may provide optional suggestions and costs as a separate listing.

Bidder shall provide firm price proposal for project with breakout cost of sections as listed:

1. Software Cost:

1.1.1. All licensed conveyed Data Acquisition /Analysis software.

1.1.2. National Instruments LabVIEW interface with full communication.

1.1.3. SCRAMNet Interface with full communication ability.

1.1.4. Configuration of basic delivered system.

2. Hardware Cost of:

2.1.1. Data Recorder

2.1.2. 4 channel CAN Module to support CAN 2.0 A/B High Speed.

2.1.3. AC/DC Power Supply to power all instrumentation modules.

2.1.4. 16 Analog Inputs (+/-) 10 VDC

2.1.5. 4 Frequency / Speed Probe Measurement Channels.

2.1.6. 8 Type E Thermocouple.

2.1.7. 16 Type J Thermocouple.

2.1.8. 16 Type K Thermocouple.

2.1.9. 2 Discrete Digital Outputs.

2.1.10. 3 Discrete Digital Inputs.

2.1.11. 4 Accelerometer (Vibration) Transducer Inputs.

2.1.12. RS-485 MODBUS interface with ability to communicate with up to a 32 devices (standard).

2.1.13. All Standard Inter-Connecting Cabling w TEDS T/C Capability

3. Documentation:

4. Recommended Standard Training:

5. Shipping:

Optional Post Warranty Yearly Service Contract:

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN
INSPECT AT
INSPECT BY
ACCEPT AT
ACCEPT BY
0001
Destination
Government
Destination
Government

Section F - Deliveries or Performance

DELIVERY INFORMATION

CLIN
DELIVERY DATE
QUANTITY
SHIP TO ADDRESS
DODAAC / CAGE
0001
31-MAY-2017
1
N/A

FOB: Destination

CLAUSES INCORPORATED BY REFERENCE

52.247-32
F.O.B. Origin, Freight Prepaid
FEB 2006

Section G - Contract Administration Data

CLAUSES INCORPORATED BY FULL TEXT

252.232-7003ELECTRONIC SUBMISSION OF PAYMENT REQUESTS AND RECEIVING REPORTS (JUN 2012)
(a) Definitions. As used in this clause--
(1) Contract financing payment and invoice payment have the meanings given in section 32.001 of the Federal Acquisition Regulation.
(2) Electronic form means any automated system that transmits information electronically from the initiating system to all affected systems. Facsimile, e-mail, and scanned documents are not acceptable electronic forms for submission of payment requests. However, scanned documents are acceptable when they are part of a submission of a payment request made using Wide Area WorkFlow (WAWF) or another electronic form authorized by the Contracting Officer.
(3) Payment request means any request for contract financing payment or invoice payment submitted by the Contractor under this contract.
(4) Receiving report means the data required by the clause at 252.246-7000, Material Inspection and Receiving Report.
(b) Except as provided in paragraph (c) of this clause, the Contractor shall submit payment requests and receiving reports using WAWF, in one of the following electronic formats that WAWF accepts: Electronic Data Interchange, Secure File Transfer Protocol, or World Wide Web input. Information regarding WAWF is available on the Internet at https://wawf.eb.mil/ .
(c) The Contractor may submit a payment request and receiving report using other than WAWF only when--
(1) The Contracting Officer administering the contract for payment has determined, in writing, that electronic submission would be unduly burdensome to the Contractor. In such cases, the Contractor shall include a copy of the Contracting Officer's determination with each request for payment;
(2) DoD makes payment for commercial transportation services provided under a Government rate tender or a contract for transportation services using a DoD-approved electronic third party payment system or other exempted vendor payment/invoicing system (e.g., PowerTrack, Transportation Financial Management System, and Cargo and Billing System);
(3) DoD makes payment for rendered health care services using TRICARE Encounter Data System (TEDS) as the electronic format; or
(4) When the Governmentwide commercial purchase card is used as the method of payment, only submission of the receiving report in electronic form is required.
(d) The Contractor shall submit any non-electronic payment requests using the method or methods specified in Section G of the contract.
(e) In addition to the requirements of this clause, the Contractor shall meet the requirements of the appropriate payment clauses in this contract when submitting payments requests.
252.232-7006WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (MAY 2013)
(a) Definitions. as used in this clause--
"Department of Defense Activity Address Code (DoDAAC)" is a six position code that uniquely identifies a unit, activity, or organization.
"Document type" means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF). "Local processing office (LPO)" is the office responsible for payment certification when payment certification is done external to the entitlement system.
(b) Electronic invoicing. The WAWF system is the method to electronically process vendor payment requests and receiving reports, as authorized by DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports. (c) WAWF access. To access WAWF, the Contractor shall--
(1) Have a designated electronic business point of contact in the System for Award Management at https://www.acquisition.gov; and
(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this Web site.
(d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the "Web Based Training" link on the WAWF home page at https://wawf.eb.mil/.
(e) WAWF methods of document submission. Document submissions may be via Web entry, Electronic Data Interchange, or File Transfer Protocol.
(f) WAWF payment instructions. The Contractor must use the following information when submitting payment requests and receiving reports in WAWF for this contract/order:
(1) Document type. The Contractor shall use the following document type(s).
_______________________COMBO______________________________________________
(Contracting Officer: Insert applicable document type(s). Note: If a "Combo" document type is identified but not supportable by the Contractor's business systems, an "Invoice" (stand-alone) and "Receiving Report" (stand-alone) document type may be used instead.)
(2) Inspection/acceptance location. The Contractor shall select the following inspection/acceptance location(s) in WAWF, as specified by the contracting officer.
________________________SEE SECTION E_____________________________________
(Contracting Officer: Insert inspection and acceptance locations or "Not applicable.")
(3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system.
Routing Data Table*
Field Name in WAWFData to be entered in WAWF
Pay Official DoDAAC:_______N64142 ___________
Issue By DoDAAC:_______N00421 ___________
Admin DoDAAC:_______N00421 ___________
Inspect By DoDAAC:_______N00421 ___________
Ship To Code:_______N00421 ___________
Ship From Code:________N/A______________
Mark For Code:________ N/A _____________
Service Approver (DoDAAC):________ N/A _____________
Service Acceptor (DoDAAC):________ N/A _____________
Accept at Other DoDAAC:_______ N/A _____________
LPO DoDAAC:_______ N/A _____________
DCAA Auditor DoDAAC:_______ N/A ______________
(*Contracting Officer: Insert applicable DoDAAC information or "See schedule" if multiple ship to/acceptance locations apply, or "Not applicable.")
(4) Payment request and supporting documentation. The Contractor shall ensure a payment request includes appropriate contract line item and subline item descriptions of the work performed or supplies delivered, unit price/cost per unit, fee (if applicable), and all relevant back-up documentation, as defined in DFARS Appendix F, (e.g. timesheets) in support of each payment request.
(5) WAWF email notifications. The Contractor shall enter the email address identified below in the "Send Additional Email Notifications" field of WAWF once a document is submitted in the system.

__________________ @NAVY.MIL______________________________________

(Contracting Officer: Insert applicable email addresses or "Not applicable.")

(g) WAWF point of contact. (1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity's WAWF point of contact. For Navy WAWF questions call DFAS Customer Care 1-800-756-4571 option 6
(2) For technical WAWF help, contact the WAWF helpdesk at 866-618-5988.

Section I - Contract Clauses

CLAUSES INCORPORATED BY REFERENCE

52.203-7
Anti-Kickback Procedures
MAY 2014
52.212-4
Contract Terms and Conditions--Commercial Items
JAN 2017
52.232-39
Unenforceability of Unauthorized Obligations
JUN 2013
52.245-1
Government Property
JAN 2017
52.245-9
Use And Charges
APR 2012
252.204-7000
Disclosure Of Information
OCT 2016
252.204-7004 Alt A
System for Award Management Alternate A
FEB 2014
252.225-7048
Export-Controlled Items
JUN 2013
252.239-7010
Cloud Computing Services
OCT 2016

CLAUSES INCORPORATED BY FULL TEXT

52.204-13SYSTEM FOR AWARD MANAGEMENT MAINTENANCE (OCT 2016)
(a) Definitions. As used in this clause--
"Electronic Funds Transfer (EFT) indicator" means a four-character suffix to the unique entity identifier. The suffix is assigned at the discretion of the commercial, nonprofit, or Government entity to establish additional System for Award Management (SAM) records for identifying alternative EFT accounts (See subpart 32.11) for the same entity.
"Registered in the System for Award Management database" means that--

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 .