Добавил:

Upload Опубликованный материал нарушает ваши авторские права? Сообщите нам.

Вуз:

Пермский национальный исследовательский политехнический университет

Предмет:

[НЕСОРТИРОВАННОЕ]

Файл:

Хорошев / ИЛП_материал_маг_02.15 / DEF STAN 00-60 / 22000200.pdf

Скачиваний:

Добавлен:

29.03.2015

Размер:

312.92 Кб

Скачать

☆

<<< < Предыдущая 1 23 / 33

DEF STAN 00-60 (PART 22)/2

Section Two. Codification

4 The Codification Process

4.1 One of the primary purposes of the NCS is to allocate a unique NSN to Items of Supply. The use of NSN for most logistics functions means that it is important that they are allocated to items early in the provisioning cycle. Allocation of NSN is achieved by a process of screening items against the national codification database - the Item of Supply Information System (ISIS) - to:

(a)Identify items that have previously been codified.

(b)Initiate the codification of items of foreign manufacture.

(c)Allocate provisional NSN to uncodified UK items.

4.2 For equipment procured using the IP method described in Part 21 of this Defence Standard, the Contractor is responsible for undertaking the screening in conjunction with the National Codification Bureau (NCB) and for notifying the Customer of NSN allocated. In the UK the NCB is known as the Defence Codification Agency (DCA). The basis for the IP process, described in Part 21 of this Defence Standard, is S2000M. However, S2000M neither covers the screening procedure nor provides for the return of codification data back to the Contractor. Therefore, the procedures contained in this Part of this Defence Standard supplant the S2000M procedure.

5 The Stages of Initial Codification.

5.1The Contractor shall carry out preparatory actions in accordance with Annex A.

5.2The Contractor shall transmit the relevant item data to DCA using the procedure detailed at Annex B.

5.3Using the procedures at Annex C, DCA will notify the Contractor of rejected submissions which failed validation checks, acknowledge successful submissions and, following screening, will notify the Contractor of:

(a)NSN and other relevant data for items whose manufacturer's details exactly match with existing item records. DCA also registers the Contractor as an authorized user of data for the relevant item records.

(b)NSN and other relevant data for items whose manufacturer's details potentially match existing item records.

(c)Provisionally allocated NSN for items with a UK CAGE code (DED 046) attached, whose details did not match with existing item records.

DEF STAN 00-60 (PART 22)/2

(d) ‘No Match’ foreign items, which have been referred to the appropriate foreign NCB for codification action.

5.4The Contractor shall take corrective action for rejected submissions using the procedure at Annex D.

5.5The Contractor shall take action in response to outputs from DCA which follow an accepted submission, including the analysis of partial matches, using the procedure detailed at Annex E.

5.6DCA will respond, with respect to resubmitted items, in accordance with the procedure at Annex F.

5.7The Contractor shall notify the Customer of the allocated NSN by populating IPL with data received from DCA.

6. The Contractor may deregister as an authorized data users for items that become inapplicable to a project for which they were originally registered. The deregistration procedure is at Annex G. The Contractor may choose not to deregister, particularly if it is likely that the items may be used for future projects.

7. Throughout these procedures, the use of output and input in the context of messages and status codes shall be from DCA's point of view. A consolidated list of status codes is at annex H.

8. Codification related data shall be obtained from the Logistic Support Analysis (LSA) process. The Contractor shall be able to demonstrate his compliance with this requirement by providing the populated NATO Codification Report (LSA-650), if requested, the format of which is contained in annex C to Part 0 of this Defence Standard; this report may otherwise be generated in-house by MOD to check compliance.

9. Due to the current data requirements of the ISIS database, data elements unique to this Part of this Defence Standard are used in the data interchange between the Contractor and DCA. These are detailed at Annex J.

DEF STAN 00-60 (PART 22)/2

Collation Page

DEF STAN 00-60 (PART 22)/2

ANNEX A

PREPARATORY ACTIONS BY THE CONTRACTOR

A.1 The Contractor shall contact DCA and agree a method of communications in accordance with the Appendix to this Annex.

A.2 The Contractor shall include any NSN, identified during interrogation of ISIS or other relevant database, in his initial data submission to DCA. For items which have not been codified, the Contractor shall ensure that items are allocated Approved Item Names, selected from A Cod P3. Where no suitable Approved Item Name can be selected, the Contractor's own description, using reverse nomenclature, for the items shall be used and the Item Name Code (DED 183) given the value ‘77777’. If the Contractor is unable to identify an NSN for an item, the Contractor shall select an appropriate NATO Supply Class (NSC), selected from the A Cod P2, for inclusion in the initial data submission.

A.3 The Contractor may also use these procedures for initiating an enquiry of records on the ISIS database where no ISIS database facility is available to the Contractor via CD-ROM or on-line.

A.4 The Contractor shall apply to DCA for the NATO Codification Project Code (NCPC) that has been allocated for a project, and the applicable UK Submitter Code.

A.5 The Contractor shall ensure that part numbers and CAGE, shall be that of the original equipment manufacturer, or that of the organization that exercises design control over vendor items, where such control is required for the application of the items on a particular project.

A.6 The Contractor shall include only spareable items in any submission of data to the National Codification Bureau. The Contractor shall submit the item identified by the Primary Reference Number if two or more wholly interchangeable, spareable parts can be used at a single location in an equipment breakdown. The NSN returned by DCA for this item shall then apply to all of the items in the interchangeable group. This shall only apply when the interchangeability (DED 645; S2000M TEI ICY) Code is 9).

A.7 The Contractor shall ensure that part numbers are, wherever possible, fully definitive.

A.8 If the Contractor wishes to include an NSN in an initial submission, he shall ensure that its associated part number and CAGE already exists on the ISIS record for that NSN.

A.9 The Contractor shall ensure that where the CAGE starts and ends with a numeric then the NCB field is to be completed as ‘00’ for US manufacturers and ‘21’ for Canadian manufacturers. DCA help should be obtained in the differentiation between input.

A.10 Codification Contact Point. Further information on NATO Codification, including the allocation of NSCM and NCPC, can be obtained from:

A-1

DEF STAN 00-60 (PART 22)/2 ANNEX A (CONCLUDED)

Head of Codification

Defence Codification Agency

Ministry of Defence

Kentigern House

65 Brown Street

GLASGOW G2 8EX

Telephone: 0141-224-2093

A-2

DEF STAN 00-60 (PART 22)/2

APPENDIX A TO ANNEX A

COMMUNICATIONS TECHNIQUES

A/A.1 The purpose of this appendix is to set out the means of data transfer between the Contractor and DCA.

COMMUNICATION METHODS

A/A.2 The method of exchanging data is limited to:

(a)Electronic (on-line) transfer.

(b)Magnetic tape.

(c)Floppy disks.

ELECTRONIC (ON-LINE) TRANSFER

A/A.3 Electronic (on-line) transfer is the preferred option and is limited to file transfer. The method is:

(a)Connect to the Hoskyns Devizes Data Centre using the Defence Packet Switched Network (DPSN). Usage of the DPSN is provided free of charge by MOD. Installation of tail circuits from the Contractor's site into the DPSN, and encryption, is also provided by MOD.

(b)The Contractor will provide X25 protocol with ICL emulation to run on his hardware. This must incorporate File Transfer Facility (FTF).

(c)If the Contractor wishes to use this option, he should contact Head of IT, DCA. DCA will give advice to the Contractor and initiate proceedings through the appropriate MOD channels.

A/A.3.1 If the Contractor has already established connections different from the above, he may continue to use them for the foreseeable future.

MAGNETIC TAPE

A/A.4 Media specification, internal labelling and external labelling shall conform to S2000M, Appendix 2, Section A2-4 - Communication Methods, Paragraphs 5.2, 5.3 and 5.4 with the following limitations:

(a)Mode - 9 track 6250 bpi.

(b)Encoding - EBCDIC.

A/A-1

DEF STAN 00-60 (PART 22)/2

APPENDIX A TO ANNEX A (CONTINUED)

FLOPPY DISKS

A/A.5 Media specification, internal labelling and external labelling shall conform to Specification 2000M, Appendix 2, Section A2-4, Paragraphs 6.2, 6.3 and 6.4 with the following limitations:

(a)Compatible Operating system - MS-DOS.

(b)5.25 inch Disks - double sided high density, 135 tracks per inch, 1.2 megabytes.

A/A.6 Header and trailer messages shall only be used for electronic (on-line) transfer. Headers and trailers shall be formatted as detailed below:

(a) Transmission Header Record (ZZH)

Record size - 23 characters.

FIELD SPECIFICATIONS

SER	POSITION		LEVEL	FIELD NAME	SIZE	PIC	VALUE	REMARKS
NO							RANGE
	FROM	TO

01	1	3	03	Record Header			ZZH	Mandatory
					3	X

02	4	6	03	Sender Code			Note 1	Mandatory
					3	X

03	7	9	03	Recipient Code			Note 1	Mandatory
					3	X

04	10	15	03	Transmission Date			yymmdd	Mandatory
					6	9

05	16	19	03	Project Code			Note 2	Mandatory
					3	X

06	19	23	03	Transmission				Mandatory
				Control Number	5	9

NOTE 1: Serials 02 and 03

WHL - GKN Westland Helicopters

RRO - Rolls Royce ( RR1, 2, 3 dependant on how many sites )

BAE - British Aerospace ( BA1, 2, 3 i.e. BA1 = B.Ae Salmesbury )

A/A-2

DEF STAN 00-60 (PART 22)/2

APPENDIX A TO ANNEX A (CONTINUED)

DCA - DCA Glasgow

LKD - Lockheed Martin Aeronautical Systems

NOTE 2: Serial 05

NATO codification project codes to be used are the same as those used within the data record layouts.

In the case of projects which are not multi-national using these procedures, the NCPC will be allocated by DCA.

(b) Transmission Trailer Record (ZZT)

Record size - 13 characters.

FIELD SPECIFICATIONS

SER	POSITION		LEVEL	FIELD NAME	SIZE	PIC	VALUE	REMARKS
NO							RANGE
	FROM	TO

01	1	3	03	Record Header			ZZT	Mandatory
					3	X

02	4	8	03	Transmission				Mandatory
				Control Number	5	9

03	9	13	03	Record Count				Mandatory,
					5	9		includes
								header and
								trailer

A/A-3

DEF STAN 00-60 (PART 22)/2

APPENDIX A TO ANNEX A (CONCLUDED)

Collation Page

A/A-4

DEF STAN 00-60 (PART 22)/2

ANNEX B

PROCEDURE FOR THE CONTRACTOR INITIAL SUBMISSION OF ITEM DATA TO DCA

B.1 The Contractor shall transmit data for spareable items contained in draft Initial Provisioning Lists to DCA in accordance with the timescales shown in the flowchart at Appendix A to this Annex.

B.2 The Contractor shall compile and transmit, using the previously agreed method of data interchange, Input Header Format (IHR) and Initial Input Format (PDR) messages, as described in Appendices B and C of this Annex. The Input PDR message shall contain, as a minimum, the mandatory and conditional elements as detailed in Appendix C of this Annex.

B.3 The Contractor shall set the Input PDR message Status Code to:

A - Initial submission

L - Initial submission as a result of decision taken at Pre-assessment meeting. Y - Enquiry submission

B-1

DEF STAN 00-60 (PART 22)/2

ANNEX B (CONCLUDED)

Collation Page

B-2

UK PROCEDURAL FLOWCHART

SERIAL	ACTION	IPL	DCA	FOREIGN	CUSTOME	LATEST	REMARKS
NO		PRODUCING		NCB	R	TIME
		CONTRACTOR			SERVICE	(DAYS)
1.	AC/135 establish a codification Sub-Group to manage NATO						This serial applies only to major projects.
	codification aspects of the project.

2. The IP Guidance Conference is held.

3.	Upon request from a NATO nation, or an AC/135 Sub-Group,	This serial applies only to certain NATO or common
	the NATO International Staff assigns a NATO Codification	projects. For non-NATO/common projects, DCA will
	Project Code (NCPC).	allocate a dummy NCPC.
3.1	DCA installs a suspense file to control the progress of	National rules on the formatting of the suspense file will
	codification for the project, if required (national or multi-	apply.
	national partner-agreed rules apply).

3.2DCA obtains AC/135 Form No 7 template details from IPL producing contractor.

SERIAL

ACTION

IPL

DCA

FOREIGN

CUSTOME

LATEST

REMARKS

PRODUCING

NCB

TIME

CONTRACTOR

SERVICE

(DAYS)

The contractor transits draft IPL data, for items where reason

TRANS-

1. The contractor transmits to DCA the initial IHR record

for selection is other than Ø to DCA and using service

MISSION

and/or initial PDR record containing as a minimum:

logistics agencies.

DATE (T)

a. NSNs for which the contractor is not registered as an

authorized data receiver within the project (if

appropriate), together with the related NSCMs, part

numbers and IPPN.

b. For items where the NSN is not known:

(1)

IPPN

(2)

NSCM

(3)

Part Number

(4)

Proposed NSC

(5)

Description for Part (includes item name)

2. The item name will be that contained in the ACodP-3.

3. All manufacturer's part numbers are to be fully identifying and are to be those of the true manufacturer.

4. Input PDR record Status Code is A or L

4.1	DCA allocates Document Control Serial Numbers (DCSN) to	T+3
	each line entry received that pass the validation checks.

4.2DCA informs contractor of the details of the DCSNs that have been allocated.

T+6	IAK record. Status Code B.

4.3DCA informs contractor of the line entries that did not pass the validation checks.

T+6	IAK record. Status Code 0, 1, 2, 3 or 9.

4.4DCA informs contractor of those items that did not attract a line entry.

T+6	IAK record. Status Code 5, 6, 7, or 8.

SERIAL

ACTION

IPL

DCA

FOREIGN

CUSTOME

LATEST

REMARKS

PRODUCING

NCB

TIME

CONTRACTOR

SERVICE

(DAYS)

4.5

Contractor corrects the errors and resubmits the input to DCA

T+20

Initial 1 HR and/or PDR records. Status Code A or K.

as at Serial 4.

DCA screens all items submitted by the contractor with an

To DCA at

T+7

NSN, checking that the NIIN is on ISIS.

Serial 6

where no

NSN is

quoted

5.1

Where a foreign NSN is quoted that is not on ISIS, or the part

T+9

Shuttle PDR record Status Code G.

number quoted is not on the ISIS record for the foreign NSN

or the foreign NSN is cancelled, DCA initiates LSA action

5.2

and informs the contractor.

Where a UK NSN is quoted that is not on ISIS DCA notifies

T+9

Shuttle PDR record Status Code 4.

the contractor.

foreign

NCB

at Serial 6.3

5.3

Where a UK NSN is quoted that is recorded on ISIS as

T+9

Shuttle PDR record Status Code P.

5.4

cancelled, DCA notifies the contractor.

1. Contractor to confer with DCA where mismatch is

The contractor resolves mismatching NSNs and/or supporting

T+30

data returned as a result of Serials 5.2 and 5.3 resubmits the

disputed.

corrected data to DCA, using original DCSN or submits a

2. Shuttle PDR record Status Code A or K.

request for the item to be codified as a Serial 4.

5.5

DCA compares submitted data with that held on ISIS for the

T+9

NSN concerned.

SERIAL

ACTION

IPL

DCA

FOREIGN

CUSTOME

LATEST

REMARKS

PRODUCING

NCB

TIME

CONTRACTOR

SERVICE

(DAYS)

5.6

DCA registers the contractor as an authorized data receiver for

From Ser 4.5

T+9

1. Contractors are to be considered authorized data

those NSNs where the NSN and all supporting data is correct

receivers of:

and transmits the relevant data to the contractor.

a. NSN

Item Name

INC

NSCM

Part Number

f. RNCC

g. RNVC

2. Shuttle PDR record Status Code C and TCD message.

5.7

DCA registers the contractor as an authorized data receiver for

T+9

See remarks at Serial 5.6.

those NSNs where the NIIN and the NSCM plus part number

agree, making the necessary changes to the NSC, INC or

2. For those line entries submitted with a NSN that have

Description For Part and transmits the relevant data to the

not been cleared at Serials 5.1, 5.2, 5.3, 5.6 or 5.7 the NSN

contractor.

is now disregarded and the line entry is dealt with using the

NSCM and part number.

DCA extracts the relevant data to enable screening of all

T+9

All items are to be screened by NSCM and manufacturer's

recommended items (for all countries) without an NSN, and

part number in order to determine 'Exact Matches'. If no

those submitted with an NSN that have not been cleared at

'Exact Match' is found, items with a UK NSCM are to be

Serials 5.1, 5.2, 5.3, 5.6 and 5.7, against the ISIS database

further screened by manufacturer's part number to

extracting 'Exact' and 'Potential Matches'.

determine 'Potential Matches'.

6.1

For all 'Exact Matches' DCA transmits the relevant data to the

T+9

See Remarks 1 at Serial No 5.6.

contractor and registers the contractor as and authorized data

receiver.

Shuttle PDR record Status Code D and TCD messages.

6.2

DCA extracts data for all remaining items and sorts part

From Serial

T+9

numbers into own and other countries, using the NSCM as the

5.1

key.

SERIAL

ACTION

IPL

DCA

FOREIGN

CUSTOME

LATEST

REMARKS

PRODUCING

NCB

TIME

CONTRACTOR

SERVICE

(DAYS)

6.3

DCA submits all remaining items of foreign manufacture to

T+10

A NATO Form AC/135 No 7, quoting the contract number,

the appropriate foreign NCB for codification. This includes

is to be dispatched together with the LSA request(s) using

those line entries for which there are 'Potential Matches' on

Priority Indicator Code 'A'.

the ISIS file.

NOTE:

The Priority Indicator Code used in input transactions

(between NCBs) is to indicate the precedence and response

time allowed for transaction processing to ensure

employment of the timeframe agreed upon.

6.4

DCA sorts all remaining items of UK manufacture into

To DCA at Serial

T+10

'Potential matches' and 'No Matches'.

DCA refers all UK 'Potential Matches' to the contractor.

T+12

Shuttle PDR record Status Code I and TCD messages.

7.1

Contractor resolves 'Potential Matches' using the appropriate

T+33

technical expertise, enlisting the aid of DCA, if necessary.

7.2

Where a contractor identifies that a 'Potential Match' relates to

T+35

1. This action will take place as soon as possible, but no

a specific line entry, they will submit a request to be registered

later than at Serial No 12 of this flowchart.

as an authorized data receiver. The Reference Number

Contractor resubmits shuttle PDR record Status Code K

Justification Code is left blank.

quoting NSN.

2. DCA response is shuttle PDR record Status Code C.

7.3

Where none of the NSNs offered is acceptable and the item,

T+35

Contractor resubmits shuttle PDR record Status Code K,

therefore, must be codified, the contractor will submit a

completing NSC field together with RNJC of 1 to show

request for codification, together with the Reference Number

that codification action is required. Depending upon

Justification Code (RNJC) set to '1'.

resources of staff, time and information, DCA may review

records created for UK 'no-match' items.

SERIAL

ACTION

IPL

DCA

FOREIGN

CUSTOME

LATEST

REMARKS

PRODUCING

NCB

TIME

CONTRACTOR

SERVICE

(DAYS)

DCA allocates NSNs to all 'No Match' items of national

From Serial 6.4

T+16

NSNs are to be allocated Codification Status Code (CSC)

origin.

of 'K'.

8.1

DCA transmits relevant data to the contractor, and registers

T+18

1. See Remark 1 at Serial No 5.6.

the contractor as an authorized data receiver.

2. Shuttle PDR record Status Code F.

The foreign NCB screens all items submitted by DCA for

T+17

9.1

codification, against its own database.

For 'Exact Matches', the foreign NCB registers the UK as a

T+19

user and transmits NSNs to DCA.

9.2

DCA transmits relevant data received from the foreign NCB

T+26

Shuttle PDR record Status Code H plus TCD messages.

for 'Exact Matches' to the contractor and registers the

9.3

contractor as an authorized data receiver.

The foreign NCB returns all 'Potential Matches' to DCA for

T_19

See Remarks at Serial 7.

action with the contractor, as at Serials 7 to 7.3.

9.4

The contractor resolves 'Potential Matches' and returns to

T+47

See Remarks at Serial Nos 7.2 and 7.3

DCA.

9.5

DCA resubmits requirements to foreign NCB.

T+47

DCA action will be LAU request where a NSN has been

agreed or LSA with RNJC of 1 where no NSN has been

agreed (Serial 6.3).

SERIAL

ACTION

IPL

DCA

FOREIGN

CUSTOME

LATEST

REMARKS

PRODUCING

NCB

TIME

CONTRACTOR

SERVICE

(DAYS)

9.6

The foreign NCB codifies 'No Match' items, registering UK as

T+82

The NATO Form AC/135 No 27 is used to reject a

a user, and transmits NSNs and supporting data and forwards

request for codification, or to inform of a change of data

any NATO Forms AC/135 No 27 to DCA.

used.

Latest time is T+122 for re-submittals with RNJC of 1.

10.

DCA transmits NSNs and forwards any informative NATO

T+90

See Remark 1 at Serial 5.6.

Forms AC/135 No 27 to the contractor, as they are received,

and registers the contractor as an authorized data receiver.

Shuttle PDR record Status Code E or H plus TCD

records and hard copy Form 27 as appropriate.

10.1

DCA transmits NATO Forms AC/135 No 27 which are rejects

T+95

Shuttle PDR record Status Code J and hard copy Form 27.

to the contractor for resolution and the re-input of new

11.

codification requests as necessary.

Formal IPL produced.

T+100

12.

The Pre-Assessment Meeting (PAM) is held.

T+120

A representative of DCA may take part in the Pre-

Assessment Meeting.

12.1

Additional codification requests, necessitated by decisions

T+130

Submission to be in accordance with Serial No 4 of this

made at the Pre-Assessment Meeting, are submitted by the

flowchart, thereafter Serials 5 to 9 apply. Initial input PDR

13.

contractor to DCA.

record Status Code is 'L'.

The contractor prepares and transmits the master IPL as

T+180

required by the Project Office.

13.1

The contractor takes appropriate action with DCA to de-

Shuttle PDR record Status Code M.

required.

DCA will return a shuttle PDR record Status Code 4 if

the NIIN is not on ISIS.

SERIAL	ACTION	IPL	DCA	FOREIGN	CUSTOME	LATEST	REMARKS
NO		PRODUCING		NCB	R	TIME
		CONTRACTOR			SERVICE	(DAYS)

13.2DCA takes appropriate action with other NCBs to delete user interest in respect of those items notified at Serial No 13.1.

14.	DCA creates IPPN Status Reports for internal management	T+194
	information.
15.	Following decision to purchase, all Services initiate User	The precise timing and methodology for this action is yet
	Registration with their home NCBs (in UK-DCA), using the	to be agreed.
	reconciliation input from the using Service Logistics
	Database.
	Database.

16.After Master IPL is ‘stabilized’, full codification is initiated via DCA.

17.Full codification continues, as required, at the appropriate NCB or DCA.

18.DCA transmits change details received, to contractors for those NSNs on which the contractor is recorded as an authorized data receiver.

INPUT HEADER FORMAT (IHR)

The Record Size is 74 Characters

				FIELD SPECIFICATIONS				REMARKS

SERIAL	POSITION		LEVEL	FIELD NAME	SIZE	PICTURE	VALUE
NO							RANGE
	FRO	TO
	M

01	1	3	03	RECORD HEADER	3	X	IHR	Mandatory

02	4	12	03	INITIAL PROVISIONING	9	X		Mandatory (IPPN)
				PROJECT NUMBER

03	13	15	03	NATO CODIFICATION PROJECT	3	X		Mandatory (NCPC)
				CODE

04	16	21	03	MESSAGE TYPE	6	X		Not Essential (MT)

05	22	23	03	ISSUE STANDARD	2	X		Not Essential (IS)

06	24	28	03	TRANSMITTER OF DATA	5	X		Mandatory (TOD)

07	29	33	03	ADDRESSEE	5	X		Not Essential (A)

08	34	34	03	FILE IDENTIFIER	1	X		Not Essential (FI)


09	35	36	03	MODEL IDENTIFICATION	2	X		Not Essential (MI)

10	37	39	03	DATA RELEASE SEQUENCE	3	9		Not Essential (DRSN)
				NUMBER

11	40	45	03	DATA RELEASE DATE	6	9		Not Essential (DRD)


12	46	47	03	LANGUAGE CODE	2	X		Not Essential (LC)

13	48	66	03	ITEM PROVISIONING PROJECT	19	X		Not Essential (IPPNS)
				NUMBER SUBJECT

14	67	74	03	DATA RELEASE REFERENCE	8	X		Not Essential (DRR)

DEF STAN 00-60 (PART 22)/2

APPENDIX B TO ANNEX B (CONCLUDED)

Collation Page

B/B-2

INITIAL INPUT FORMAT (PDR)

The Record Size is 233 Characters

				FIELD SPECIFICATIONS				REMARKS

SERIAL	POSITION		LEVEL	FIELD NAME	SIZE	PICTURE	VALUE
NO							RANGE
	FROM	TO

01	1	3	03	RECORD HEADER	3	X	PDR	Mandatory

02	4	4	03	CHANGE CODE	1	X		Not Required (CHG)

03	5	36	03	PART NUMBER	32	X		Mandatory (PN)

04	37	41	03	NATO SUPPLY CODE FOR	5	X		Mandatory (NSCM)
				MANUFACTURERS

05	42	171	03	DESCRIPTION FOR PART	130	X		Mandatory if no INC quoted (DFP)

06	172	176	03	ITEM NAME CODE	5	X		Mandatory if no Description quoted (INC)

07	177	189	03	NATO STOCK NUMBER				Comprised of Serials 08-10 (NSN)
07	177	189	03	NATO STOCK NUMBER				Comprised of Serials 08-10 (NSN)

08	177	180	05	NATO SUPPLY	4	9		Mandatory (NSC)
				CLASSIFICATION

09	181	182	05	NATO CODIFICATION BUREAU	2	9		Mandatory if US or CA NSCM (NCB Code)
				CODE				(NOTE: Serials 09 and 10 comprise the NIIN)

10	183	189	05	ITEM IDENTIFICATION	7	9		Optional (IIN)
				NUMBER

11	190	190	03	REFERENCE NUMBER	1	X		Not Required (RNCC)
				CATEGORY CODE
				CATEGORY CODE

12	191	191	03	REFERENCE NUMBER	1	9		Not Required (RNVC)
				VARIATION CODE

13	192	192	03	REFERENCE NUMBER	1	9		Not Required (RNJC)
				JUSTIFICATION CODE

				FIELD SPECIFICATIONS				REMARKS
				FIELD SPECIFICATIONS				REMARKS

SERIAL	POSITION		LEVEL	FIELD NAME	SIZE	PICTURE	VALUE
NO							RANGE
	FROM	TO
14	193	194	03	UNIT OF ISSUE	2	X		Optional (UI)

15	195	196	03	UNIT OF MEASURE	2	X		Optional (UM)

16	197	200	03	QUANTITY PER UNIT OF ISSUE	4	X		Optional (QPUI)

17	201	207	03	DOCUMENT CONTROL SERIAL				Comprised of Serials 18-19 (DCSN)
				NUMBER

18	201	203	05	NATO CODIFICATION PROJECT	3	X		Mandatory (NCPC)
				CODE

19	204	207	05	RECORD NUMBER	4	X		Not Required

20	208	209	03	REPEAT COUNT	2	9		Not Required


21	210	210	03	STATUS CODE	1	X	A or L	Mandatory
21	210	210	03	STATUS CODE	1	X	A or L	Mandatory

22	211	211	03	DFP CHANGE INDICATOR	1	X		Not Required

23	212	212	03	INC CHANGE INDICATOR	1	X		Not Required

24	213	213	03	NSC CHANGE INDICATOR	1	X		Not Required

25	214	214	03	NIIN CHANGE INDICATOR	1	X		Not Required

26	215	223	03	INITIAL PROVISIONING	9	X		Mandatory (IPPN)
				PROJECT NUMBER

27	224	228	03	OTHER MATCH COUNT	5	9		Not Required

28	229	233	03	JULIAN DATE	5	9		Not Required

DEF STAN 00-60 (PART 22)/2

ANNEX C

PROCEDURE FOR DCA TO RESPOND TO THE CONTRACTOR'S INITIAL SUBMISSION

C.1 DCA will acknowledge the Contractor's initial submission that successfully pass the validation test by transmitting an Initial Output Format (IAK) message, in the format at Appendix A to this Annex, with a Status Code of B and a 7 digit Document Control Serial Number (DCSN). The DCSN is a combination of the 3 digit Project Code and the 4 digit Line Entry number. If input passes validation there will always be a Line Entry (within the Project) allocated to the item and this DCSN must always be used for re-submittals or manual queries relating to this item. Items which fail validation (except for Status Codes 5, 6, 7 or 8) will also have a line entry allocated which, again must be used for all resubmittals/queries.

C.2 Where the message fails validation, data will not be screened against the ISIS database and an IAK message will be transmitted by DCA to the Contractor, with one of the following reject status codes:

(a)Status Code 0. NSC missing

(b)Status Code 1. Part Number missing

(c)Status Code 2. NSCM missing or invalid

(d)Status Code 3. Item Name Code or Description for Part missing

(e)Status Code 5. Input Status Code invalid

(f)Status Code 6. Limit of 1,336,336 records for a single NCPC will be exceeded

(g)Status Code 7. No IHR message received prior to transmission of PDR message

(h)Status Code 8. Invalid IPPN or NCPC

C.3 Following screening against the ISIS database, an Output PDR message will be transmitted by DCA to the Contractor in the format at Appendix B to this Annex with Status Code set according to the results of the screening as detailed below:

C.3.1 UK reference quoted but no NIIN

C.3.1.1 If there is an exact match, the Status Code will be set to D and, if the input Status Code was A or L the Contractor will be added to the ISIS record as lead contractor.

C.3.1.2 If there are potential matches, details from the records of a maximum of 10 NSNs will be transmitted to the Contractor. For each NSN, there will be an Output PDR message with the Status Code set at I, together with up to 30 Total Characteristic Data (TCD) messages containing the characteristics of the matching NSN, enabling the Contractor to compare

C-1

DEF STAN 00-60 (PART 22)/2

ANNEX C (CONTINUED)

technical features of the matching items against the data held by them. The format for the TCD message is at Appendix C to this Annex.

C.3.1.3 If there are no matches and the input Status Code was A or L, skeleton records will be created on the ISIS database with provisional NSNs. Regardless of the input Status Code, the Output Status Code will be F.

C.3.2 UK NIIN and UK reference quoted

C.3.2.1 If the NIIN is recognized and the Reference is recorded against the NIIN, it will be treated as an exact match. The Output Status Code will be set to C. If the Input Status Code was Y, the Contractor will not be added as a lead contractor.

C.3.2.2 If the NIIN is not recognized, the Output Status Code is set at 4. Resubmission will be required after examination of the details by the Contractor.

C.3.2.3 If the NIIN is recognized, or is cancelled, and the reference is not recorded against the NIIN, the NIIN will be ignored, and the reference actioned in accordance with clause C.3.1 above.

C.3.3 Foreign NIIN and foreign reference quoted

C.3.3.1 If there is an exact match, the Output Status Code is set to C.

C.3.3.2 If the NIIN is recognized, but the reference quoted is not recorded against the NIIN, and if the Input Status Code was A or L, a Codification and Registration as User (LSA) transaction will be created and sent to the appropriate foreign NCB. The Output Status Code will be set to G. If the Input Status Code was Y, the input will be treated as if there were no NIIN on input, ie the reference will be screened as in Clause C.3.1 above.

C.3.3.3 If the NIIN is not recognized, or is cancelled, and if the Input Status Code was not A or L, an LSA transaction will be created. The Output Status Code will be set to G. If the Input Status Code was Y, the input will be treated as if there were no NIIN on input, ie the reference will be screened as in Clause C.3.1 above.

C.3.4 Foreign reference quoted but no NIIN

C.3.4.1 If there is an exact match, the Output Status Code will be set to D. If the Input Status Code was Y, the Contractor will not be added as a lead contractor.

C.3.4.2 If there are potential matches, details from the records of a maximum of 10 NSNs will be transmitted to the Contractor. Each NSN, there will be an Output PDR message with the Status Code set to I, together with up to 30 TCD messages containing the characteristics of the matching NSN, enabling the Contractor to compare technical features of the matching items against the data held by them. The format for the TCD message is at Appendix C to this Annex.

C-2

DEF STAN 00-60 (PART 22)/2

ANNEX C (CONTINUED)

C.3.4.3 If there are no matches and the Input Status Code is Y, the Output Status Code will be set at 0. If the Input Status Code is A or L, an LSA transaction will be created and sent to the appropriate foreign NCB. The Output Status Code will be set to G.

NOTE: It must be noted that where the NSCM starts and ends with a numeric then the NCB field is to be completed as ‘00’ for US manufacturers or ‘21’ for Canadian manufacturers. DCA help should be obtained in the differentiation between input.

C.3.5 Foreign NIIN and UK reference quoted

C.3.5.1 If there is an exact match, the Output Status Code will be set at C, otherwise the input will be treated as per Clause C.3.1 above.

C.3.6 UK NIIN and foreign reference quoted

C.3.6.1 If there is an exact match, the Output Status Code will be set to C.

C.3.6.2 If the NIIN is not recognized, the Output Status Code will be set at 4. Resubmission will be required after examination of the details.

C.3.6.3 If the NIIN is recognized, or is cancelled, but the foreign reference is not recorded against that NIIN, an LSA transaction is created. The Output Status Code will be set to G. See the Note to Clause C.3.4 above with respect to NSCMs that start and end with a numeric.

C.3.7 NIIN quoted but no reference (PDR Status Code Y)

C.3.7.1 If the NIIN is not recognized the Output Status Code will be set to 0.

C.3.7.2 If the NIIN is recognized but is cancelled, the Output Status Code will be set to P.

C.3.7.3 If the NIIN is recognized and not cancelled, the Output Status Code will be set to C.

C.4 Result of LSA Action. In response to the LSA action, as described in Clauses C.3.3.2, C.3.3.3 and C.3.4.3, foreign NCB will send DCA Forms AC/135 No 27 notifying the results of the screening. DCA will notify the Contractor of the outcome of the LSA action as follows:

C.4.1 Informative Form 27. DCA will transmit a PDR message with Status Code E and forward a copy of the Form 27, containing relevant item details, by post.

C.4.2 Reject Form 27. If for any reason the LSA request is rejected by the foreign NCB, DCA will transmit a PDR message with Status Code J and forward a copy of the Form 27, containing the reason for the rejection, by post.

C-3

DEF STAN 00-60 (PART 22)/2

ANNEX C (CONCLUDED)

Collation Page

C-4

INITIAL OUTPUT FORMAT (IAK)

The Record Size is 233 Characters

				FIELD SPECIFICATIONS				REMARKS

SERIAL	POSITION		LEVEL	FIELD NAME	SIZE	PICTURE	VALUE
NO							RANGE
	FROM	TO

01	1	3	03	RECORD HEADER	3	X	IAK

02	4	4	03	CHANGE CODE	1	X		(CHG)

03	5	36	03	PART NUMBER	32	X		(PN)

04	37	41	03	NATO SUPPLY CODE FOR	5	X		(NSCM)
				MANUFACTURERS

05	42	171	03	DESCRIPTION FOR PART	130	X		(DFP)

06	172	176	03	ITEM NAME CODE	5	X		(INC)

07	177	189	03	NATO STOCK NUMBER				Comprised of Serials 08-10 (NSN)
07	177	189	03	NATO STOCK NUMBER				Comprised of Serials 08-10 (NSN)

08	177	180	05	NATO SUPPLY	4	9		(NSC)
				CLASSIFICATION

09	181	182	05	NATO CODIFICATION BUREAU	2	9		(NCB Code)
				CODE				) NIIN)

10	183	189	05	ITEM IDENTIFICATION	7	9		(IIN)
				NUMBER				)

11	190	190	03	REFERENCE NUMBER	1	X		(RNCC)
				CATEGORY CODE
				CATEGORY CODE

12	191	191	03	REFERENCE NUMBER	1	9		(RNVC)
				VARIATION CODE

13	192	192	03	REFERENCE NUMBER	1	9		(RNJC)
				JUSTIFICATION CODE

				FIELD SPECIFICATIONS				REMARKS
				FIELD SPECIFICATIONS				REMARKS

SERIAL	POSITION		LEVEL	FIELD NAME	SIZE	PICTURE	VALUE
NO							RANGE
	FROM	TO
14	193	194	03	UNIT OF ISSUE	2	X		(UI)

15	195	196	03	UNIT OF MEASURE	2	X		(UM)

16	197	200	03	QUANTITY PER UNIT OF ISSUE	4	X		(QPUI)

17	201	207	03	DOCUMENT CONTROL SERIAL				Comprised of Serials 18-19 (DCSN)
				NUMBER

18	201	203	05	NATO CODIFICATION PROJECT	3	X		(NCPC)
				CODE

19	204	207	05	RECORD NUMBER	4	X

20	208	209	03	REPEAT COUNT	2	9


21	210	210	03	STATUS CODE	1	X
21	210	210	03	STATUS CODE	1	X

22	211	211	03	DFP CHANGE INDICATOR	1	X

23	212	212	03	INC CHANGE INDICATOR	1	X

24	213	213	03	NSC CHANGE INDICATOR	1	X

25	214	214	03	NIIN CHANGE INDICATOR	1	X

26	215	223	03	INITIAL PROVISIONING	9	X		(IPPN)
				PROJECT NUMBER

27	224	228	03	OTHER MATCH COUNT	5	9

28	229	233	03	JULIAN DATE	5	9

SHUTTLE RECORD DATA FORMAT (PDR)

The Record Size is 233 Characters

				FIELD SPECIFICATIONS				REMARKS

SERIAL	POSITION		LEVEL	FIELD NAME	SIZE	PICTURE	VALUE
NO							RANGE
	FROM	TO

01	1	3	03	RECORD HEADER	3	X	PDR

02	4	4	03	CHANGE CODE	1	X		(CHG)

03	5	36	03	PART NUMBER	32	X		(PN)

04	37	41	03	NATO SUPPLY CODE FOR	5	X		(NSCM)
				MANUFACTURERS

05	42	171	03	DESCRIPTION FOR PART	130	X		(DFP)

06	172	176	03	ITEM NAME CODE	5	X		(INC)

07	177	189	03	NATO STOCK NUMBER				Comprised of Serials 08-10 (NSN)
07	177	189	03	NATO STOCK NUMBER				Comprised of Serials 08-10 (NSN)

08	177	180	05	NATO SUPPLY	4	9		(NSC)
				CLASSIFICATION

09	181	182	05	NATO CODIFICATION BUREAU	2	9		(NCB Code)
				CODE				) NIIN)

10	183	189	05	ITEM IDENTIFICATION	7	9		(IIN)
				NUMBER				)

11	190	190	03	REFERENCE NUMBER	1	X		(RNCC)
				CATEGORY CODE
				CATEGORY CODE

12	191	191	03	REFERENCE NUMBER	1	9		(RNVC)
				VARIATION CODE

13	192	192	03	REFERENCE NUMBER	1	9		(RNJC)
				JUSTIFICATION CODE

				FIELD SPECIFICATIONS				REMARKS
				FIELD SPECIFICATIONS				REMARKS

SERIAL	POSITION		LEVEL	FIELD NAME	SIZE	PICTURE	VALUE
NO							RANGE
	FROM	TO
14	193	194	03	UNIT OF ISSUE	2	X		(UI)


15	195	196	03	UNIT OF MEASURE	2	X		(UM)

16	197	200	03	QUANTITY PER UNIT OF ISSUE	4	X		(QPUI)

17	201	207	03	DOCUMENT CONTROL SERIAL				Comprised of Serials 18-19 (DCSN)
				NUMBER


18	201	203	05	NATO CODIFICATION PROJECT	3	X		(NCPC)
				CODE

19	204	207	05	RECORD NUMBER	4	X

20	208	209	03	REPEAT COUNT	2	9


21	210	210	03	STATUS CODE	1	X	Not A
21	210	210	03	STATUS CODE	1	X	Not A
							or L

22	211	211	03	DFP CHANGE INDICATOR	1	X

23	212	212	03	INC CHANGE INDICATOR	1	X

24	213	213	03	NSC CHANGE INDICATOR	1	X

25	214	214	03	NIIN CHANGE INDICATOR	1	X

26	215	223	03	INITIAL PROVISIONING	9	X		(IPPN)
				PROJECT NUMBER

27	224	228	03	OTHER MATCH COUNT	5	9

28	229	233	03	JULIAN DATE	5	9

CHARACTERISTICS INFORMATION RECORD (TCD)

The Record Size is 131 Characters

				FIELD SPECIFICATIONS					REMARKS

SERIAL	POSITION		LEVEL	FIELD NAME	SIZE	PICTURE	VALUE
NO							RANGE
	FRO	TO
	M

01	1	3	03	RECORD HEADER	3	X	TCD

02	4	7	03	NATO SUPPLY	4	9		(NSC) )	(NOTE: Serials 02 and 03
				CLASSIFICATION				) (NSN)	comprise the NSN)

03	8	16	03	NATO ITEM IDENTIFICATION	9	9		(NIIN)
				NUMBER

04	17	25	03	FILLER	9	X	SPACES

5	26	32	03	DOCUMENT CONTROL SERIAL	7	X		(DSCN)
				NUMBER
				NUMBER

06	33	33	03	TYPE OF ITEM	1	X
				IDENTIFICATION

07	34	43	03	FILLER	10	X	SPACES


08	44	48	03	ITEM NAME CODE	5	X		(INC)

09	49	52	03	RECORD SEQUENCE	4	9

10	53	56	03	PRIMARY ADDRESS CODE	4	X		(PAC)

11	57	58	03	SEPARATOR	2	X	**
11	57	58	03	SEPARATOR	2	X	**

12	59	90	03	REQUIREMENT STATEMENT	32	X

13	91	91	03	SEPARATOR	1	X	*

14	92	131	03	REPLY DATA	40	X

DEF STAN 00-60 (PART 22)/2

APPENDIX C TO ANNEX C (CONCLUDED)

Collation Page

C/C-2

DEF STAN 00-60 (PART 22)/2

ANNEX D

PROCEDURES FOR THE CONTRACTOR FOLLOWING A REJECTED SUBMISSION

D.1 Before the Contractor's submission is screened against the ISIS database, a number of checks are carried out for the presence of mandatory data elements and the validity of certain data. Any submission failing these checks will result in the cessation of processing and an output message from DCA to the Contractor with an appropriate reject status code indicating the reason for the rejection. The Contractor shall take action, depending on the status code, as follows:

D.1.1 Where the Status Code on the IAK message is 5, 6, 7 or 8, the Contractor shall examine their input details, correct as necessary, and re-input as a first submission.

D.1.2 Where the Status Code on the lAK message is 0, 1, 2 or 3, the Contractor shall record the Record Number as part of the DCN, examine their input details, correcting as necessary and re-submit a PDR record with a Status Code of K.

D.2 Even though a submission may pass these checks, the Contractor's data may be rejected for other reasons, eg. rejection by a foreign NCB. These will be notified in a PDR message, and the Contractor's action is dealt with in Annex E.

D-1

DEF STAN 00-60 (PART 22)/2

ANNEX D (CONCLUDED)

Collation Page

D-2

DEF STAN 00-60 (PART 22)/2

ANNEX E

PROCEDURES FOR THE CONTRACTOR ON RECEIPT OF OUTPUT FROM DCA

E.1 Where an lAK record with Status Code B has been received, the PDR Status Code will be C, D, F, G or I. No resubmission is required.

E.2 Rejects will be returned as for Status Code A and L inputs. The PDR Status Code will be 0, 1, 2, 3, 5, 6, 7 or 8. All re-inputs from these rejects should be treated as resubmissions.

E.4 PDR Status Code C, D or F

E.4.1 The Contractor shall record the additional data provided in the Output PDR Message.

E.4.2 PDR Status Code C or D. Action for these items is complete, unless subsequently notified that the NSN has been cancelled.

E.4.3 PDR Status Code of F. If the Contractor subsequently identifies errors in supplementary data on the record (NSC, NSCM, INC and/or Description), a resubmission PDR with a Status Code of Z can be input with the corrected data. It should be noted that the NIIN and reference on this resubmission MUST be identical to the original PDR (Status Code A or L).

E.4.4 The Contractor shall examine the data provided on the Output PDR Message. Where errors are found, the Contractor shall correct and resubmit the data as necessary with the Status Code on the Input PDR Message set to K (if the previous Status Code was A, K or L) or Z (if the previous Status Code was Z).

E.5 PDR Status Code I

E.5.1 A Status Code of I on an Output PDR Message indicates that potential matches have been found. Multiple Output PDR records with different NSN, up to a maximum of 10, will be transmitted with the number of potential matches in excess of the 10 shown in the Other Match Count field. In addition, up to 30 TCD records for each PDR record will be transmitted, each TCD record containing a characteristic associated with the NSN recorded on it.

E.5.2 The Contractor shall compare the characteristics of the TCD records supplied, against the characteristics of the items being used in the project. Matches included in the Other Match Count field will have to be obtained by interrogation of the ISIS database. This comparison can result in either:

E.5.2.1 One of the NSN being accepted for the project item. The Contractor shall transmit an Input PDR Message with the Status Code set at K; the NSC, NCB and NIIN fields completed to that of the accepted NSN; and the Reference Number Justification Code field left blank.

E-1

DEF STAN 00-60 (PART 22)/2

ANNEX E (CONCLUDED)

E.5.2.2 None of the NSN being accepted for the project item and a new NSN being required. The Contractor shall transmit an Input PDR Message with the Status Code set to K; the NSC field completed; the NCB and IIN fields left blank (unless the submitted NSCM starts and ends with a numeric, in which case the NCB field shall be completed. See the Note to Clause E.4.1; and the Reference Number Justification Code field set to 1.

E.5.3 If the Contractor finds evidence of duplicate NSN amongst the potential matches, he should notify DCA by off-line means for investigation and resolution.

E.6 PDR Status Code G

E.6.1 Status Code G is used to notify the Contractor that LSA (request for codification by a foreign NCB) action will be taken by DCA.

E.7 PDR Status Code E.

E.7.1 The Contractor shall await delivery of the AC/135 Form No 27 and record the relevant data.

E.8 PDR Status Code J.

E.8.1 The Contractor shall await delivery of the AC/135 Form 27, investigate the reason for the rejection, and resubmit accordingly.

E.9 Resubmissions. The Contractor should note that resubmissions will be validated to ensure that:

E.9.1 An IPPN, NCPC and Record Number are present.

E.9.2 The record is already present on the suspense file.

E.9.3 That there is a Description For Part, INC, NSC and reference present.

E-2

DEF STAN 00-60 (PART 22)/2

ANNEX F

PROCEDURE FOR DCA TO RESPOND TO THE CONTRACTOR'S RESUBMISSION

F.1 After validation of these resubmissions, action is taken by DCA, based upon the Reference Number Justification Code field, the NSCM field, the NCB field and the IIN field, where completed.

F.1.1 Reference Number Justification Code field blank

F.1.1.1 Where the NSN submitted is a UK NSN then an exact match should occur and DCA will transmit an Output PDR Message with the Status Code set to C.

F.1.1.2 Where the NSN submitted is a Foreign NSN either:

F.1.1.2.1 An exact match with foreign NIINs held on ISIS can occur and DCA will transmit an Output PDR Message with the Status Code set to C,

or,

F.1.1.2.2 DCA will initiate a LAU transaction and transmit an Output PDR Message with the Status Code set to N. No action is required by the Contractor apart from recording the Status Code.

F.1.2 Reference Number Justification Code field set to 1

F.1.2.1 Where the NSCM submitted is a UK, or non-NATO NSCM then an Output PDR Message will be transmitted with the Status Code set to F.

F.1.2.2 Where the NSCM submitted is a foreign NSCM, DCA will raise a LSA transaction and transmit an Output PDR Message with the Status Code set at G.

F.2 PDR Status Code Z

F.2.1 In response to a Status Code Z from the Contractor, DCA will check that the NIIN and reference on the Input are the same as that recorded on the AECMA suspense file. If not, DCA will reject with a Status Code of X. A reject with a Status Code W will be returned if the previous Status Code from DCA to the Contractor was F or Z or if the NIIN on ISIS had been fully codified. If the amendment is successful, Output PDR messages will be transmitted to the Contractor as follows:

F.2.1.1 If the data to be changed is NSC, INC and description, the Status Code will be set to V.

F.2.1.2 If the data to be changed is NSCM and the NSCM still relates to non-foreign items (ie the NSCM begins with a ‘K’, ‘U’, ‘S’ or ‘I’), the Status Code will be set to V.

F-1

DEF STAN 00-60 (PART 22)/2

ANNEX F (CONCLUDED)

F.2.1.3 If the data to be changed is NSCM and the NSCM relates to another country, the Status Code will be set to G. Additionally, the UK NSN will be cancelled as erroneous, and an LSA request will be raised on the foreign NCB.

F-2

DEF STAN 00-60 (PART 22)/2

ANNEX G

DE-REGISTRATION PROCEDURE

G.1 The Contractor shall transmit data for items which have previously been codified and for which the Contractor is already registered as an Authorised Data Receiver if the input relates to a DCSN which has not previously identified the NSN. This is because DCA will retain a cross-reference between DCSN and NSN so that although the Contractor will only be added once an Authorised Data receiver for any given NSN, any amendment to that NSN could produce several identical output messages relating to different DCSN. It will also allow the Contractor to de-register for a particular DCSN without having to check that this was the only item within all AECMA Spec 2OOOM Projects for which they were added as an Authorised Data Receiver - DCA will only delete the Authorised Data Receiver from the NSN if all DCSN for the NSN and for that Contractor have been de-registered.

G.2 As soon as the Contractor responsible for an IPL is aware that an item whose UK or foreign NSN is no longer required for the project, it may initiate a PDR message with the Status Code set at M.

G3 Reasons which give rise to this action include:

G.3.1 None of the nations participating in the project require the item as an item of supply.

G.3.2 The item has been replaced by another (eg modification).

G.3.3 Certain incorrect data was provided on the first and subsequent submissions (see possible amendments by Status Code ‘Z’).

G.4 In addition to the normal checks, the Input NIIN will be checked against that held on ISIS and, if they are not the same, DCA will transmit an output PDR message with the Status Code set at 9. The submitter shall examine the details, correct as necessary and re-input as at Paragraph G.2.

NOTE: If a Contractor de-registers from a provisional NSN which was created from the original screening submission (see Serial no 8 of the Flowchart at Appendix A to Annex B) and the same NSN is not linked to any other Authorised Data Receivers, DCA will cancel the NSN.

G-1

DEF STAN 00-60 (PART 22)/2

ANNEX G (CONCLUDED)

Collation Page

G-2

DEF STAN 00-60 (PART 22)/2

ANNEX H

STATUS CODES LIST

INPUT STATUS CODES

A First submission of IPL data by Contractor.

KResubmittal from the Contractor in response to Status Codes I, J, T and 0, 1, 2, 3, 4 and 9.

LContractor places additional request as the result of decision taken at Pre-Assessment Meeting.

MContractor requests de-registration as authorized data receiver for the NSN quoted.

YContractor requests enquiry (by reference or NIIN) - no data changes to ISIS records will occur.

ZContractor requests amendments to NSC, NSCM or INC/Desc on CSC K record. ADVISORY STATUS CODES

BDCA notification of record number part of DCSN - output after initial processing phase for first submissions.

CDCA has found exact screening match (CONTRACTOR HAD INPUT NIIN). If the input Status Code was Y, the submitter will not be added as a lead contractor.

DDCA has found exact screening match (CONTRACTOR DID NOT INPUT NIIN). If the Input Status Code was Y, the submitter will not be added as a lead contractor.

EDCA has received informative NATO Form AC/135 No 27.

FNo screening match. DCA has allocated provisional NSN to codification Status Code K.

GLSA request has been raised on foreign NCB.

HLSA or LAU request pertaining to only one NSN received from foreign NCB.

IPotential match found by DCA or foreign NCB.

JNATO Form AC/135 No 27 reject received from foreign NCB.

NLAU request sent to foreign NCB.

ONo screening match. A provisional NIIN has NOT been allocated.

PNIIN is a cancelled NIIN.

H-1

DEF STAN 00-60 (PART 22)/2

ANNEX H (CONTINUED)

QA change has been received to the reference to the NSN for which the Contractor is an authorized data receiver.

RA change has been received to the NSC and/or inc and/or Description For Part to the NSN for which the Contractor is an authorized data receiver.

SA change has been received to the characteristics to the NSN for which the Contractor is an authorized data receiver.

TAn NSN for which the Contractor is an authorized data receiver has been cancelled without replacement.

UAn NSN for which the Contractor is an authorized data receiver has been cancelled with replacement.

VData amended as requested (Successful output from Input Status Z).

REJECT STATUS CODES

Ø NSC missing on submission from the Contractor.

1Part number missing on submission from the Contractor.

2NSCM missing or invalid NSCM on submission from the Contractor.

3INC invalid or INC/Description For Part missing on submission from the Contractor.

4NIIN quoted by the Contractor not on file (output after processing through ISIS).

5Invalid Status Code.

6Record number will exceed NCPC limit of 1,336,336 records.

7Header record not on suspense file.

8Invalid IPPN/NCPC.

9Incorrect NIIN quoted (Status Code M submission is quoting the wrong NIIN).

WAmendment request (Status Z) does not relate to a K record.

XNIIN or Part Number on input (Status Z) different from data on Status F record. NOTES:

1. Status Codes Ø, 1, 2, 3, 4 and 9 rejects will be returned with the record number completed.

H-2

DEF STAN 00-60 (PART 22)/2

ANNEX H (CONTINUED)

2.Status Code 6 rejects will always be returned without a completed record number.

3.Status Code 5, 7 and 8 rejects will be returned without a completed record number for first submission inputs (STATUS CODE A or L inputs) but will retain the record number where the input was a resubmittal.

H-3

DEF STAN 00-60 (PART 22)/2

ANNEX H (CONCLUDED)

Collation Page

H-4

DEF STAN 00-60 (PART 22)/2

ANNEX J

DATA ELEMENTS LIST

J.1 The procedures detailed in this Part of this Defence Standard use S2000M data elements as well as data elements that are unique. The latter are identified below in the format:

DATA ELEMENT TITLE

FIELD FORMAT

DATA ELEMENT DEFINITION

J.2 The field format is the specification for the length, type, positional justification and decimal placement of a data element and follows the convention for the Data Dictionary in Part 0 of this Defence Standard.

J.3 Data Elements.

CHANGE INDICATOR

1 X

A code indicating that there has been a change to the input description

DOCUMENT CONTROL SERIAL NUMBER

- - - -

A composite data element representing the last 7 characters of the Document Control Number which is used in NATO Data Exchange and made up of the NATO Codification Project Code and the Record Number (See definitions elsewhere in this annex).

NATO CODIFICATION PROJECT CODE

3 X F -

A code assigned by the NATO Secretariat to identify codification requests relating to a particular project. The first 2 characters identify the project, and the third character identifies part of the project, or the prime contractor. It forms the first 3 characters of the Document Control Serial Number. DCA allocate dummy codes for national projects.

J-1

DEF STAN 00-60 (PART 22)/2

ANNEX J (CONTINUED)

OTHER MATCH COUNT

5 N F -

A count of the potential matches in excess of 10 which have already been output by DCA to the submitter.

PRIMARY ADDRESS CODE

4 X F -

A code assigned to identify, in abbreviated form, the item characteristic that requires identification.

RECORD HEADER

3 X F -

A code used to identify the type of message.

RECORD NUMBER

4 X F -

A non-significant number that forms the last 4 characters of the Document Control Serial Number.

RECORD SEQUENCE

4 N F -

An incremental number used to identify the order of the information contained within data elements: Primary Address Code, Requirement Statement and Reply Data for the specified NSN.

REPEAT COUNT

2 N F -

A count of PDR records which have been output in reply to a submitted input.

REPLY DATA

40 X F -

An item's characteristic, in free text, provided in response to a Primary

Address Code requirement.

J-2

DEF STAN 00-60 (PART 22)/2

ANNEX J (CONTINUED)

REQUIREMENT STATEMENT

32 X F -

A free text explanation of the Primary Address Code requirement

STATUS CODE

1 X F -

A code used to identify the reason for an IAK or PDR message being sent.

TYPE OF ITEM IDENTIFICATION

1 X F -

A code indicating the extent to which the requirements of a mandatory Primary Address Code have been answered

JULIAN DATE

5 N F -

A representation of the data. The first 2 digits represent the year; the last 3 digits represent the day of the year, numbered consecutively from 1, starting on 1 January. Eg 96032=1 Feb 96.

J-3

DEF STAN 00-60 (PART 22)/2

ANNEX J (CONCLUDED)

Collation Page

J-4

Collation Page

DEF STAN 00-60 (PART 22)/2

	except for sale purposes. The
Published by and obtainable from: following conditions must be observed:
Ministry of Defence	1 The Royal Coat of Arms and the
Directorate of Standardization	publishing imprint are to be
Kentigern House	omitted.
65 Brown Street	2 The following statement is to be
GLASGOW G2 8EX	inserted on the cover:
	‘Crown Copyright. Reprinted by
Tel No: 0141-224 2531	(name of organization) with the
Fax No: 0141-224 2503	permission of Her Majesty's
	Stationery Office.’
	Requests for commercial reproduction
	should be addressed to MOD Stan 1,
	Kentigern House, 65 Brown Street,
	Glasgow G2 8EX

The following Defence Standard file reference relates to work on this Standard - D/D Stan/384/04/22

Contract Requirements

When Defence Standards are incorporated into contracts users are responsible for their correct application and for complying with contract requirements.

Revision of Defence Standards

Defence Standards are revised when necessary by the issue either of amendments or of revised editions. It is important that users of Defence Standards should ascertain that they are in possession of the latest amendments or editions. Information on all Defence Standards is contained in DEF STAN 00-00 (Part 3) Section 4, Index of Standards for Defence Procurement - Index of Defence Standards and Specifications published annually and supplemented periodically by Standards in Defence News. Any person who, when making use of a Defence Standard encounters an inaccuracy or ambiguity is requested to notify the Directorate of Standardization without delay in order that the matter may be investigated and appropriate action taken.

<<< < Предыдущая 1 23 / 33

Соседние файлы в папке DEF STAN 00-60

#
29.03.2015263.88 Кб3503000200.pdf
#
29.03.20151.13 Mб4210000300.pdf
#
29.03.2015222.25 Кб3911000300.pdf
#
29.03.201593.43 Кб3220000400.pdf
#
29.03.201588.38 Кб2921000300.pdf
#
29.03.2015312.92 Кб2922000200.pdf
#
29.03.2015196.72 Кб2923000200.pdf
#
29.03.2015448.64 Кб2824000300.pdf
#
29.03.2015137.94 Кб2925000200.pdf