RFP-ACT-SACT-19-35_ASSET_TRACKING_CAPABILITY_CAMPAIGN_AMENDMENT_1.pdf

PDF 830 KB Posted May 13, 2019

Attached to: Contractor Support Asset Tracking
Solicitation number: RFP-ACT-SACT-19-35
Issued by: NATO HQ Supreme Allied Commander

About this file

From the source

AMENDMENT 1

View the file

Other files

File	Type	Posted
RFP-ACT-SACT-19-35_ASSET_TRACKING_CAPABILITY_CAMPAIGN.pdf	PDF	May 6, 2019

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

NATO UNCLASSIFIED

RFP-ACT-SACT-19-35

Bidder’s proposal must be based on full compliance with the terms, conditions and requirements of the RFP and all future clarifications and/or amendments. The bidder may offer variations in specific implementation and operational details provided that the functional and performance requirements are fully satisfied. In case of conflict between the compliance statement and the detailed evidence or explanation furnished, the detailed evidence/comments shall take precedence/priority for the actual determination of compliance.

Minor or non-substantial deviations may be accepted. Substantial changes shall be considered non responsive.

Request for Proposal

Part 1 Bidding Instructions

Amendment #1

Minor or non-substantial deviations may be accepted. Substantial changes shall be considered non responsive.

TABLE OF CONTENTS

1. General

2. Classification

3. Definitions

4. Eligibility

5. Duration of the Contract

6. Exemption of Taxes

7. Amendment or Cancellations

8. Bidder Clarifications

9. Bid Closing Date

10. Bid Validity

11. Contents of Proposal

12. Proposal Submission

13. Late Bid

14. Bid Withdrawal

15. Bid Evaluation

16. Proposal Clarifications

17. Award

18. Communications and Contacts

19. NATO Secret Document Storage

20. Point of Contact

ENCLOSURES:

1. SOW

2. Proposal Checklist

3. Address Label

4. Compliance Statement

5. Past Performance

6. Mandatory Price Proposal format

Minor or non-substantial deviations may be accepted. Substantial changes shall be considered non responsive.

This page intentionally blank

Minor or non-substantial deviations may be accepted. Substantial changes shall be considered non responsive.

PART 1 BIDDING INSTRUCTIONS

1. General.

This is a Firm Fixed Price service contract in accordance HQ SACT General Terms and Conditions. Contract Award is contingent upon funding availability.

2. Classification.

This RFP is a NATO UNCLASSIFIED document.

3. Definitions

(a) The “Prospective Bidder”, shall refer to the entity that has completed and returned the Enclosure of the transmittal letter of this RFP, and has indicated thereon its intention without commitment, to participate in this

RFP.

(b) The term “Bidder”, shall refer to the bidding entity that has completed a bid in response to this RFP.

(d) The term “Contracting Officer” designates the official who executes this

RFP on behalf of HQ SACT.

(e) “Contracting Officer`s Technical Representative” or “COTR” is the official who is appointed for the purpose of determining compliance of the successful bid, per the technical specifications.

(f) The term “HQ SACT” shall refer to Supreme Headquarters Allied

Command Transformation.

(g) The term “ACT” shall refer to Allied Commander Transformation.

(h) The term “NATO”, shall refer to the North Atlantic Treaty Organisation.

(i) The term “days” as used in this RFP shall, unless otherwise stated, be interpreted as meaning calendar days.

(j) The term “Habitual Residence”, means HQ SACT, Norfolk, Virginia, VA

23511.

Minor or non-substantial deviations may be accepted. Substantial changes shall be considered non responsive.

4. Eligibility.

This RFP is open to selected companies:

(a) Established in a North Atlantic Treaty Organisation Alliance member nation.

(b) Working in the required field of study and legally authorised to operate the United States of America and European Union, at the time of bidding.

5. Duration of Contract

(a) The contract awarded shall be effective upon date of award.

6. Exemption of taxes.

(a) In accordance with the agreements (Article VIII of the Paris Protocol dated, 25 August 1952) goods and services under this contract are exempt from taxes, duties and similar charges.

7. Amendment or Cancellation.

(a) HQ SACT reserves the right to amend or delete any one or more of the terms, conditions or provisions of the RFP prior to the date set for bid closing. A solicitation amendment or amendments shall announce such action.

(b) HQ SACT reserves the right to cancel, at any time, this RFP either partially of in its entirety. No legal liability on the part of HQ SACT shall be considered for recovery of costs in connection to bid preparation. All efforts undertaken by any bidder shall be done considering and accepting, that no costs shall be recovered from HQ SACT. If this RFP is cancelled any/all received bids shall be returned unopened, per the bidder’s request.

8. Bidder Clarifications.

(a) Prospective Bidders should seek clarification at their earliest convenience. Any explanation regarding the meaning or interpretation of this

RFP, terms, clause, provision or specifications, shall be requested in writing, from the Contracting Officer. The Contracting Officer must receive such requests for clarification no later than 7 calendar days prior to the bid closing date.

Minor or non-substantial deviations may be accepted. Substantial changes shall be considered non responsive.

(b) Information in response to a request for clarification to a prospective bidder shall be furnished to all prospective bidders as a Question and

Answer amendment. All such amendments shall be incorporated into this

RFP. Oral Interpretations shall not be binding. All questions must be received NLT 23 May 2019, 1200 hrs Eastern Standard Time, Norfolk, Virginia, USA.

9. Bid closing date.

(a) Bids shall be received at HQ SACT, Purchasing and Contracting Office, no later than 3 June 2019, 1200 hours, Eastern Standard Time, Norfolk, Virginia, USA. No bids shall be accepted after this time and date.

10. Bid Validity.

(a) Bids shall be remain valid for a period of one hundred and twenty days

(120) form the applicable closing date set forth within this RFP. HQ

SACT reserves the right to request an extension of validity. Bidder shall be entitled to either grant or deny this extension of validity; HQ SACT shall automatically consider a denial to extend the validity as a withdrawal of the bid.

11. Content of Proposal.

The proposal shall consist of 1 electronic copy (1 PDF document containing each of the documents below excluding the price proposal) and 5 paper copies

(to include price proposal). Submissions must be received prior to 3 June

2019, 1200 hours, Eastern Standard Time, Norfolk, Virginia, USA.

(a) The bidders full name address, Point of Contacts, Telephone, Fax number and Internet site;

(b) Proposal checklist (See Enclosure #2)

(d) Completed Annex A & Supporting Key Personnel Resumes

(e) Company Price proposal, (Enclosure # 6)

(f) Any other technical information to determine whether proposed services, terms and conditions comply with all the requirements of this RFP.

Minor or non-substantial deviations may be accepted. Substantial changes shall be considered non responsive.

12. Proposal Submission.

(a) E-mail proposals shall be submitted in a single PDF document to include only the Technical volume. Hard copy proposals shall be submitted in two separately packaged and sealed volumes, Technical and Price prior to the established bid closing date/time.

(b) Proposal packages should be delivered to HQ SACT via e-mail, courier, or hand carried with confirmation of delivery. Suppliers wishing to hand carry submissions MUST have access to deliver on-base at a military installation without escort.

(d) Prices shall be on a Firm Fixed Price Basis

(e) It is the sole responsibility of the interested company to review any Q & A that may be issued in support of this solicitation, prior to bid submission.

(f) No oral bids or oral modifications or telephonic bids shall be considered.

(g) It is the ultimate responsibility prior to submission that all proposal submissions are reviewed to ensure they meet the technical and administrative specifications and that offers meet the limitations and expressed conditions.

13. Late Proposals.

(a) It is solely the bidder`s responsibility that every effort is made to ensure that the proposal reaches HQ SACT prior to the established closing date and time. All late bids shall be returned to the offering company unopened.

Only if it can be unequivocally demonstrated that the late arrival of the bid package was the result of NATO staff negligence (mishandling) shall the bid be considered.

14. Bid Withdrawal.

(a) A bidder may withdraw their bid up to the date and time specified for bid closing. Such a withdrawal must be completed in writing or facsimile, with attention to the HQ SACT Contracting Officer. The proposal shall be returned unopened, at the expense of the company.

Minor or non-substantial deviations may be accepted. Substantial changes shall be considered non responsive.

15. Bid Evaluation.

Bid Evaluation.

(a) The evaluation of bids and determination as to the responsiveness and technical adequacy or technical compliance, of the products or services requested, shall be the responsibility of HQ SACT. Such determinations shall be consistent with the evaluation criteria specified in the RFP. HQ

SACT is not responsible for any content that is not clearly identified in any proposal package.

(b) Proposals shall be evaluated taking into consideration of the following factors;

Successful administrative submission of bid packages and requested

Enclosures 2-6, as listed in this RFP. (Pass/Fail).

Successful determination of Technical compliance based upon criteria contained in Annex A.

Lowest Price Offer.

Acceptance of HQ SACT General Terms and Conditions.

16. Proposal Clarifications.

(a) During the entire evaluation process HQ SACT reserves the right to discuss any bid with the order to clarify what is offered and interpretation of language within the bid, to resolve in potential areas of non-compliance.

17. Award.

HQ SACT intends to award a firm fixed price contract to the Lowest Priced

Technically Compliant offeror.

HQ SACT will collect information from references provided by the Offeror in regard to its past performance. The Offeror must provide the information requested for performance risk evaluation, or affirmatively state that it possesses no directly related or similar past performance.

Firms lacking relevant past performance shall provide at least one Letter of

Reference.

Minor or non-substantial deviations may be accepted. Substantial changes shall be considered non responsive.

HQ SACT reserves the right to negotiate minor deviations to the listed

General Terms and Conditions to this RFP.

18. Communications.

(a) All communication related to this RFP, between a prospective bidder and

HQ SACT shall be only be through the nominated HQ SACT Contracting

Officer. Designated contracting staff shall assist the HQ SACT

Contracting Officer in the administrative process. There shall be no contact with other HQ SACT personnel in regards to this RFP. Such adherence shall ensure Fair and Open Competition with equal consideration and competitive footing leverage to all interested parties.

19. Point of Contact is;

Tonya Bonilla, Contracting Officer 757-747-3575 tonya.bonilla@act.nato.int or Catherine Giglio, R&D Contracting Officer 757-747-3856

Catherine.giglio@act.nato.int

All correspondence shall be forward to;

HQ SACT, BUDFIN BRANCH

Purchasing & Contracting, Contracting Officer

RFP-ACT-SACT-19-35

ATTN. Tonya Bonilla

Tonya.bonilla@act.nato.int

7857 Blandy Road, Suite 100, Norfolk, VA, U.S.A.

mailto:tonya.bonilla@act.nato.int mailto:Catherine.giglio@act.nato.int mailto:Tonya.bonilla@act.nato.int

This Enclosure is designed to assist the respective company provide HQ SACT with all necessary documents/information required. For clarification, please refer to Bidding instructions in part 1 of subject solicitation. Page 9

Enclosure 2

PROPOSAL CONTENT / CHECKLIST

Table of Contents

Bidder`s name, address, POC, Contact numbers, email address.

Compliance Statement.

Past performance (including References).

List of Key personnel.

Technical Proposal.

Price Proposal.

Mailing label.

Enclosure 3

(The label below is to be completed by the bidder and affixed to the exterior envelope; parcel or package mailed or deliver to ACT)

SEALED BID TO RFP-ACT-SACT-19-35

(To be opened by Contract Awards Committee (CAC Only)

Sender:

HQ SACT

IFIB-ACT-SACT-19-35

Attn: Tonya Bonilla

7857 Blandy Road, Suite 100, Norfolk, VA 23551-2490

U.S.A shall take precedence/priority for the actual determination of compliance. Minor or non-substantial deviations may be accepted. Substantial changes shall be considered non responsive.

Enclosure 4

COMPLIANCE STATEMENT TO SEALED BID IFIB-ACT-SACT-19-35

It is hereby stated that our company has read and understands all documentation issued as part of IFIB-ACT-SACT-19-35. Our company proposal submitted in response to the referenced solicitation is fully compliant with the provisions of IFIB-

ACT-SACT-19-35 and the intended contract with the following exception(s); such exemptions are considered non substantial to the HQ SACT solicitation provisions issued.

Clause Description of Minor Deviation.

(If applicable, add another page)

Company: Signature:

Name & Title: Date:

Company Bid Reference:

Bidder’s proposal must be based on full compliance with the terms, conditions and requirements of the IFIB and all future clarifications and/or amendments. The bidder may offer variations in specific implementation and operational details provided that the functional and performance requirements are fully satisfied. In case of conflict between the compliance statement and the detailed evidence or explanation furnished, the detailed evidence/comments

Enclosure 5

PAST PERFORMANCE INFORMATION FORM

(a) Contracting Agency:

(b) Contract No:

(d) Title of Contract:

(e) Description of Work Performance and Relevance to Current Acquisition (Type of facility, capacity, estimated patronage, summary of staff used):

(f) Contract Dollar Amount:

(g) Period of Performance:

(h) Name, Address, Fax and Telephone No. of Reference:

(i) Indicate Whether Reference Acted as Prime or Sub-contractor:

(j) Comments regarding compliance with contract terms and conditions:

(k) Complete Contact Information for client:

(l) Permission to contact client for reference: Yes/ No

Name/Signature of Authorized Company Official

Enclosure (6) SUBJECT: RFP-ACT-SACT-19-35 Sealed Bid Price Proposal

Please find on behalf of Insert: Company Name to provide HQ SACT with services (collectively referred as “ITEMS”), subject to the provisions, terms and conditions stated in RFP-ACT-SACT-19-35 and the “Insert : Company Name Technical proposal”, submitted in accordance with solicitation provisions.

Serial A (15 June – 01 Aug 2019) $

Serial B (15 June – 01 Sep 2019) $

Serial C (09 Sep – 13 Sep 2019 $

Serial D (16 Sep – 01 Nov 2019) $

Serial E (04 Nov – 08 Nov 2019) $

Serial F (15 Nov – 20 Dec 2019) $

Total Base Period Costs $

Serial G ( 02 Feb – 08 Feb 2020) $

Serial H ( 24 Feb – 28 Feb 2020) $

Serial I (01 May – 09 May 2020) $

Serial J (15 June – 01 Jul 2020) $

Total Option Period Costs $

Total of Base + Options $ ________________________

Please verify and acknowledge propriety of above, by duly completing signatures below.

Authorizing Company Official: Printed Name: _______________ Position: _____________Title: ___________________

Authorizing Company (Signature): ---------------------------------, Date: ---------------

Company name Witness Official:

Printed Name:

Position:

Title: Witness Signature: ----------------------------------------------------------, Date ----------

Page

10/18/201

Enclosure 1

Headquarters Supreme Allied Commander Transformation

STATEMENT OF WORK

for Deliverables in support of the planning and execution of the Allied Command Transformation’s

Asset Tracking Capability Development Campaign

1. Introduction. To meet the NATO commander’s need for in-transit visibility of key assets flowing into, within and out of a Joint Operations Area (JOA), NATO is working towards the creation of a system of interoperable asset tracking networks built upon national and NATO capabilities. Realization of the individual network components has been underway for some time. It is being achieved through the development and implementation of shared concepts, standards, procedures and designs. Together, these provide the ways to attain and maintain the compatibility, interchangeability and commonality of network components. Much of the development phase is now complete. The integration of the individual parts into a coherent whole must now be managed and coordinated.

2. Background

Previous developments.

Many of the NATO standards associated with asset tracking (eg, the application and use of barcodes, shipping labels and radio frequency identification) have existed for several years. But work has only recently been finalized that establishes the full set of policy, procedural and technical standards for asset tracking. Those standards are compliant with NATO’s data strategy in support of network enabled capability and conform to the NATO Architecture Framework. Inter-system and inter-network messaging can be undertaken using both ADat-P3 and XML-MTF (i.e., eXtensible Mark-up Language-Message Text Format) messages.

Main Stakeholders involved in the development.

NATO’s Military Committee Asset Tracking Inter-service Working Group has led the development effort. This body is staffed by subject matter experts from contributing nations, from the NATO Command structure and from the NATO Communication & Information Agency (NCIA) and the NATO Support and Acquisition Agency (NSPA). The development of products has been undertaken either by specialist technical panels of the working group or by writing teams constituted for a particular task. Some work has also been contracted directly to the NATO Communication & Information Agency or undertaken by the Message Text Formatting Capability Team, under the authority of the NATO Command, Control and Communications Board.

3. Support to Integration. NATO takes a holistic view of the development of capabilities. The name the organization gives to this conceptual approach is

DOTMLPFI (ie, Doctrine, Organization, Training, Material, Leadership, Development, Personnel, Facilities and Interoperability). Practically, this means that a programme or project is considered according to all the facets necessary to successful implementation; for example, not only the purchase of some equipment but the training of staff who will use it and the revision of procedures that indicate how the new equipment will be used within the organization. NATO intends to pursue such an approach to achievement of the required asset tracking capability. In particular, the organization plans for a multi-year programme that permits validation of the products of NATO asset tracking standardization and provides for the education and training of personnel engaged in realizing the capability. The programme will also support and encourage nations in their efforts to migrate towards the envisioned state of interoperability. Where opportunities arise during the period of the programme, and where operational justification exists, the programme may explore new methods, technologies and techniques in the field of asset tracking.

4. Aspects of NATO Asset Tracking Standardization. NATO recognizes that the tracking of assets can take place through a mixture of approaches, from the entirely manual through to the fully automated. Those approaches may be supported by a wide variety of technologies. The envisaged NATO asset tracking capability assumes at least some degree of automation. It has its basis in the concept of Automatic Identification and Data Capture (AIDC). This embodies the notion of Automatic Identification Technology (AIT), which includes the likes of barcodes, data matrices, and passive and active Radio Frequency Identification (RFID) devices. An integrated NATO asset tracking capability will be built on:

4.1. A founding conceptual basis. The conceptual keystone for asset tracking is NATO’s future Operations Logistics Chain Management (OLCM) capability. This calls for the coordination of logistic support to NATO missions. In-transit visibility contributes to the requirement for Visibility concerning the logistic resources available to the commander.

4.2. A Business Process Model (BPM) in which the requirement to exchange information is fully embedded. The future asset tracking BPM identifies the physical process activities and the information products that must be shared in order to realize network-wide in-transit visibility.

4.3. The construction of message content according to the situation that pertains within the context of the BPM, as guided by the business rules that specify the required content of the message and its distribution.

4.4. The transmission of messages in accordance with an agreed system architecture requirement.

4.5. Recognized AIT on which data is encoded using an NATO agreed format.

4.6. The physical labelling of transport packages, shipments and consignments in accordance with NATO agreed specifications.

5. Outline Requirement for Support. To ensure a successful exercise campaign, Contractor support is required. This Contractor will use key personnel with technical expertise in the application of AIT within the project:

5.1 . The specification, exchange and validation of AST messages as appropriate, based in NATO Stanag and international standards (e.g GS1). Definition of the exchanges based on the business processes.

Developing those deliverables required for each event. This requirement applies to the planning and product development stage of the project as well as to the operational conduct and analysis of an interoperability exercise and reporting stages.

5.2 . The Contractor shall ensure that the technical component of the project (format of the messages, Information exchange requirements, design of the networks, AST system architecture) supports and informs the overall conceptual design create by the logistic experts and is compliant with the business process.

5.3 The Contractor shall support SACT as the NATO Officer Scheduling Exercises. This responsibility will be discharged in line with direction and guidance provided by the Contracting Representative (COTR) appointed by ACT. Tasks will lead to such deliverables as the technical annex of the Exercise Specification (EXSPEC), the Exercise Plan (EXPLAN), the exercise aim, Exercise Objectives (EOs), the Training Objective (TO)

5.4 The Contractor shall design the technical component of the interoperability test cases defined for the exercise by SACT.

5.5 The Contractor shall support SACT during the execution of exercise control (to include the review of test cases related to message exchanges and the provision of host nation support)

5.6 The Contractor shall provide a final technical report to be included in the final ATCIC report.

6. Qualifications. Proposed key personnel must be qualified in the following respects:

6.1. Experience.

The following levels of experience are considered ‘must have’ qualifications:

6.1.1. Two years’ demonstrable project role(s) in the specification and design of an asset tracking (or ‘track and trace’) capability to be integrated within an overarching supply chain and employing active RFID technology.

6.1.2. Two years’ demonstrable and regular experience in network management, fault-finding and diagnosis associated with the system-wide implementation or application of AIT in the movement and transportation element of a supply chain environment.

6.1.3. Two years’ experience within the last five years in a logistics position that exploited the network-wide asset tracking information provided through the application of AIT in order to enhance asset tracking and supply chain network performance.

6.1.4. Two years’ experience within the last seven years working within a multinational environment.

6.1.5. Current awareness, knowledge and demonstrable experience in the application and employment of promulgated NATO standards and related civilian standards applicable to asset tracking. Relevant standards are detailed at Sub-para 10c.

There are no requirements that are considered desirable only.

Contractors must submit specific information concerning any qualifications or experience they consider pertinent to the qualification of proposed key personnel.

6.2 Deliverable Quality. It is expected that all deliverables are developed/delivered in high quality. Deliverables should be produced at the graduate level, in English using the appropriate Microsoft Office Software program.

6.3 Security. All contractor key personnel must possess a current NATO SECRET security clearance or national equivalent at the time of proposal submission.

7. Type of Contract and Period of Performance.

7.1. Type of Contract. This is a firm-fixed price deliverables contract in accordance with the General Terms and Conditions. All employer responsibilities for the Contractor Personnel performing under this contract shall lie with the Contractor.

7.2. Period of Performance. The Period of Performance is for one 7-month base period from 15 Jun 2019 through 21 December 2019 with one 12-month option period 1 January 2020 through 31 December 2020. The option period may be exercised solely at the discretion of HQ SACT based on satisfactory contractor performance, budgetary & operational requirements and Contracting Officer approval.

7.3. Surge Capability. Surge capability requirement is included to have a contract vehicle in place should emerging circumstances require a quick and temporary increase in products or deliverables. The contractor company shall be prepared to provide support for additional services in the same functional area identified above as directed and approved by the Contracting Officer. A deliverables table will be provided to identify any associated surge requirement. The estimated level of effort to complete the deliverable should not exceed 100 hours per base/option period.

Illustrative questions and answers

Q1. In what areas might the additional services be required?

HQ SACT intends to support asset tracking capability integration based on existing shared concepts, standards, procedures and designs. Where these factors change during the course of the programme, the programme may need to be adapted. Similarly, the surge capability provides opportunity to explore or experiment with new methods, technologies and techniques in the field of asset tracking, should they present themselves.

Q2. What form might the additional services take?

If additional services are required, it is likely that more extensive investigative effort will be required than is considered in the base contract requirement. This will cater for the emerging issues outlined in Q1 above. Ultimately the product of the additional services will be delivered as an extension to or modification of one of the deliverables described later in the SOW. During exercise execution, depending on the additional service concerned, there might be a requirement for a degree of oversight or control above the level initially considered to be part of the baseline requirement.

8. Contractor Supervision and Reporting: The Contracting Officer will assign a

Contracting Officer’s Technical Representative (COTR) to administer all technical contract details. The Contracting Officer has final authority (in consultation with the COTR) to determine if the contract/SOW should be amended, extended, modified or cancelled for evolving requirements, new tasking, and/or technical non-performance.

8.1. The COTR shall:

8.1.1. Resolve outstanding disputes, problems, deficiencies, and/or questions on the technical aspects of the SOW;

8.1.2. Review (and approve) all Contractor duties for completeness and accuracy;

8.1.3. Review the Contractor’s work at a minimum of monthly, or more often if needed

8.2. The COTR’s written approval of work reported and deliverables submitted is mandatory for contractor invoices to be successfully processed. The COTR shall receive a letter of appointment from the Contracting Officer that describes in detail his roles and responsibilities to which he shall sign formal acceptance.

8.3. The contractor shall submit a monthly report to the COTR and the

Contracting Officer, detailing progress on the SOW for the reporting period.

The report shall include, but not be limited to, the following information:

8.3.1. Summary of work and status of deliverables during the reporting period;

8.3.2. Contract hours expended showing a comparison with budgeted hours;

8.3.3. Current or anticipated problems/deficiencies and recommended solutions.

8.4. The COTR reserves the right to amend the reporting requirements to receive alternate/additional data and information on a more frequent or less frequent basis, and to request other reports that detail designated aspects of the work or methods to remedy problems and deficiencies.

9. Place of Performance: The Contractor is expected to perform the majority of the required work at the Contractor’s Facility or in alternate locations as per travel requirements at locations specified by the COTR.

10. Proof of Past Performance: The Contractor is to provide two past performance citations or references (for work within the past five years) to show that it has successfully completed work that is similar to or directly traceable to the requirements outlined in this SOW. The citations shall include the following information at a minimum:

10.1. Summary of work or tasks performed that is similar to or directly related to this SOW.

10.2. Status of work or tasks assigned (i.e., on-going, complete)

10.3. Date of Performance

10.4. Name of client or reference

10.5. Complete contact information for client or reference

10.6. Permission to contact client or reference.

11. Building, Installation Access

The contractor shall be fully responsible for ensuring that he/she has all needed vehicle passes and decals, individual access badges and documents for appropriate access to any NATO facility as required.

12. Electronic Devices.

All contractor personnel shall abide by the security restrictions regarding carrying and using electronic devices (e.g. laptops, cell phones) in all NATO facilities. The Contractor(s) shall be responsible for satisfying the necessary clearance requirements before bringing any such device into a NATO facility.

13. Export Control.

NATO nations have regulations and laws applying to the export of defence related goods/services originating from domestic commercial sources to foreign entities.

Usually under those laws and regulations NATO is considered a foreign entity. The requirements of this SOW are provided in order to allow the bidder/contractor the opportunity to assess the applicability of their pertinent national laws and regulations and take action as required.

Exercise and Experimentation Support in 2019

Deliverables for NATO Multinational Asset Tracking Capability Development Programme

2019 /SOW/NATO ASSET TRACKING EXERCISE SUPPORT

TECHNICAL ENGAGEMENT IN ASSET TRACKING EXERCISE

PLANNING, PREPARATION, CONDUCT AND ANALYSIS

In the tables that follow concerning the Base Period Deliverables and Option Period Deliverables, dates are given during which work on each deliverable is expected to take place. The difference between the start and end date of the period is not an indication of the number of days of effort that is thought necessary to the production of the deliverable. Rather it indicates the period during which the work necessary will be required to take place. (This provision does not apply in the case of deliverables C, E, G, H and I. These deliverables relate to conferences, surveys or the exercise execution itself. Dates in these cases indicate required days of participation and include one day of travel time prior to and after the event concerned.) Where the deliverable description may not provide an adequate idea of the expected quantity or complexity of the work involved, that deliverable has an illustrative question and answer to assist in that assessment.

1. Tasks and Deliverables

1.1. General. The contractor will participate in selected meetings for the planning, conduct and reporting of the experiment. The contractor will ensure that key personnel attend meetings fully prepared to participate in and to contribute to the meeting aims and objectives. The COTR will support this requirement by ensuring that relevant new or modified NATO standardization documentation is furnished to the Contractor. The Contractor is also expected to maintain situational awareness regarding related civilian developments. The contractor will additionally support preparation for those meetings by assisting the COTR with the development of the necessary documentation and products (as indicated in deliverable table below).

1.2. Specific Tasks. The contractor will be expected to perform the following specific tasks:

1.2.1. Maintain regular contact with the COTR concerning overall performance of the work under the contract.

1.2.2. Maintain regular contact with the COTR concerning the specifics of the work undertaken and to be undertaken.

1.2.3. Remain up to date and fully conversant with relevant NATO standards and associated commercial open standards.

1.2.4. Provide technical advice to ensure the planning of multinational asset tracking exercise activity, and experimentation if undertaken, is:

1.2.4.1. Consistent with applicable doctrine and NATO and Commercial technical standards concerning in-transit visibility of assets;

1.2.4.2. Recognizes the priorities needed to support the project’s aims and objectives and address the perspectives of participants.

1.2.4.3. Advise on the technical issues about the way to articulate the exercise and any related experimentation, with NATO exercise, education and training documentation as the basis for such communication.

1.2.4.4. Provide the technical and information architectures necessary to support planned exercises and experiments.

1.3. Preparation. To prepare for the activities and the production of deliverables, the Contractor will be expected to:

1.3.1. Be familiar with, or make himself familiar with, the following NATO publications and the open or commercial standards referenced in them:

a) GS1 General Specifications. Jan 2019

b) ISO 18000-7.

c) Allied Joint Publication 4.11 (AJP-4.11), Asset Visibility ;

d) Allied Administrative Publication 51, Edition B (AAP-51 (B)) Final Draft, Asset Tracking Business Process Model;

e) Allied Automatic Identification Technology Publication 04 (AAITP-04), Asset, Consignment and Personnel Tracking Information Exchange;

f) Allied Automatic Identification Technology Publication 06 (AAITP-06), System Architecture Requirements for Asset, Consignment and Personnel Tracking Information Exchange.

g) Standardization Agreement (STANAG) 2495, Edition 2, Data Formats for Asset Tracking;

h) STANAG 2233, Edition 3, NATO Consignment and Asset Tracking by Radio Frequency Identification;

i) STANAG 2494, Edition 3, NATO Asset Tracking Shipping Label and Associated Symbologies; and

j) STANAG 4281, Edition 2, NATO Standard Marking for Shipment and Storage.

1.3.2. Coordinate with the COTR on specific requirements and any authorities required for production of a deliverable;

1.3.3. When appropriate, and if authorized, coordinate deliverables work and outputs direct with nations or NATO entities; and

1.3.4. Participate in the coordination of exercise preparations and associated discussions as required (via email, phone or similar), instigating such communication where necessary.

1.4. Programme Events. Where the programme schedules events such as meetings, conferences or the conduct of the exercise, the Contractor will be expected to:

1.4.1. Consider and proffer to the COTR any pre-event advice felt to be necessary or helpful;

1.4.2. Provide advice and guidance on the application and interpretation of doctrine and standards related to current and future technologies used during exercise preparation and conduct events;

1.4.3. Undertake event roles as requested by the COTR;

1.4.4. Participate in and contribute, in the SME area of expertise, to daily coordination meetings during the conduct of the exercise and any experiment and site survey;

1.4.5. Participate in and contribute to the after action review during the conduct of the exercise and any experiment;

1.5. Deliverable and Programme Event Inputs and Feedback. The forms of communication by which the Contractor contributes to the programme will involve providing:

1.5.1. Verbal and written inputs to the COTR as necessary to sound working relationships and the achievement of programme aims and objectives;

1.5.2. Written inputs, comments, advice and suggestions concerning exercise and experiment documents such as the EXSPEC, the EXPLAN and any Experiment Design Document;

1.5.3. A written report on each event attended, which outlines important results, observations, conclusions, recommendations and other issues relevant to this SOW;

1.5.4. Written observations, lessons identified and strategic advice during and after the operational conduct of the exercise;

1.5.5. Contributions to the exercise first impressions report and, subsequently, the final exercise report.

Base Period Deliverables (01 May 2019 – 31 December 2019)

Serial Dates Location Task

15 June – 01Aug

Work from Contractor’s Facility

Planning & Product Development

Experiential: Based on meeting the Qualification and Experiential requirements of key personnel, the Contractor will be required to contribute asset tracking expertise and advice to Stage 1 Planning of the Exercise. This will be undertaken through the provision of further technical input to the draft of the Exercise Specifications (EXSPEC) following circulation of the draft to interested nations for review and comment and facilitate the brainstorming during the AST WG.

Deliverable: Provide within 14 calendar days of receipt of the second draft of the EXSPEC a written response to the document suggesting amendments and additional new material necessary to bring the document to final draft status. The focus of the products are the technical scenario, exchange of information, standards to be used and interoperability among the systems

Acceptance criteria: The deliverable must be provided in a form whose content is sufficient in extent and in detail to achieve the deliverable’s aim. It must be provided in an electronic format, likely, as a document produced using one or more applications from the Microsoft Office suite of products, and structured in such a fashion as to support ease of integration into the overall document.

Illustrative question and answer

Q3 How will this deliverable dovetail with its predecessor?

Based on prior review and comment on the outline of the programme, it is not expected that responses from nations to the first draft of the EXPEC will require a fundamental re-design of the programme and its parts. This deliverable will therefore add detail to its predecessor but will not be an unduly substantial effort. Once the deliverable is integrated into the whole, the result will be an EXSPEC that is more tangibly connected to the products that will succeed it and to the eventual conduct of the exercise itself. Programme certainty and preparation for the exercise will have advanced and issues raised by nations will have been addressed or will be under management.

15 June – 01 SEP

Concept & Specification of key personnel, the Contractor will be required to contribute technical asset tracking expertise and advice to Stage 2 Preparation of the Exercise. This will be undertaken through the provision of technical input (verbal and written) to the initial draft of the Exercise Plan (EXPLAN), support to the integration of that material within the wider document and review/comment of the document as it evolves.

Deliverables: Collaborate with, and provide technical written inputs to, the COTR with the objective of completing the technical aspects of the initial draft EXPLAN and integrating those technical matters with the more general elements of the plan. Specifically, the Contractor will contribute to: the development of training objectives ; the analysis of the COTR’s requirements and limitations (including the development and/or determination of technical requirements for the planning situation/scenario); Information Exchange Requirements (IERs) and an IER matrix; C2 Information Systems (C2IS) integration requirements; pre-operational conduct training requirements; operational Communications and Information Systems (CIS) requirements and constraints; real-life support requirements); the development of exercise planning guidance (including but not limited to providing guidance on scenario development, the use of networks and C2IS, the definition of the target technical standards the delivery of pre-operational conduct training, and the conduct of experimentation).

Q4 How does this deliverable relate to deliverables E to I?

Development of the EXPLAN is a significant task, though this contract is only for technical contributions to the overall effort. The work to develop the technical component of the final EXPLAN has been split between this deliverable and deliverables D to G. This is to allow for iterations in which product elements are developed, interaction with potential exercise participants on the emerging product takes place, the product is refined and further consultation occurs. Time and effort is also allowed for information gathering necessary to the creation of the final product. This means that the final EXPLAN will evolve over several months; no single deliverable provides all the work and the production effort will not be continuous. In this first deliverable, it is expected that there will be more person-to-person engagement between the COTR and the contractor than is likely in the development of later written deliverables. This will ensure the necessary alignment is maintained as the deliverable elements are developed independently and later integrated. The deliverable will be more than an outline but still a rough draft with a lot more work to be done. Its main goal will be to inform discussions at the Main Planning Conference.

09SEP – 13SEP

(tbc)

Luxembourg

Main Planning Conference expertise and advice to Stage 2 Preparation of the Exercise. This will be undertaken through preparation for and participation in the Main Planning Conference (MPC).

Deliverable: Support the COTR’s programme of work for the MPC, in particular to consider the draft EXPLAN and draft scenario; confirm technical requirements, especially with regard to system participation; develop commitments; and capture the additional technical information required to develop, refine and coordinate the draft of the technical annex of the EXPLAN and further develop the scenario. Active participation in the MPC providing direct support to the COTR as requested. This support may include the delivery of some briefs or presentations and leading syndicates or question and answer sessions and clarifying technical elements of the programme as requested by nations.

Acceptance criteria: The Contractor will afford sufficient and suitable support to the COTR in preparing for and conducting a successful MPC. The primary focus of that support will be on the MPC’s consideration of the technical aspects of the exercise. But that focus must be coordinated with the COTR’s effort to deliver a conference that addresses all aspects of the exercise in a coherent and integrated fashion. Programme certainty and preparation for the exercise will have advanced and issues raised by nations will have been addressed or will be under management. The deliverable must be provided in a form whose content is sufficient in extent and in detail to achieve the deliverable’s aim.

16 Sep– 01Nov

Planning & Product expertise and advice to Stage 2 Preparation of the Exercise. This will be achieved through the provision of further technical input to the revised draft EXPLAN following MPC, if undertaken.

Deliverable: Provide to the COTR within 15 calendar days of the date of end of the MPC a short written, outline proposal for the modifications necessary to improve the technical annex of the draft EXPLAN. Once agreed with the COTR, submit written revisions to the revised draft EXPLAN and scenario, noting any comments, remarks or concerns expressed by participating HQs or nations that are not addressed by the revisions. Contribute to the draft of the Site Survey action list and the agenda of the Coordination Conference (See serial E).

Acceptance criteria: The deliverable must be provided in a form whose content is sufficient in extent and in detail to achieve the…

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.