|
|
MOSIS Automated E-mail System Templates
MOSIS makes these e-mail templates available for customers who cannot
access the Word Wide Web to use the MOSIS
Web
Forms, or do not have an FTP client to transmit design files.
If you have access to the Word Wide Web, you will find the web forms
easier to use. Web forms alow you to transmit design layouts, and
support all the functions of the automated e-mail system but one: you
must use the automated e-mail system to send a layout design by e-mail
if you do not have an FTP client.
Cut and paste the appropriate template into a blank e-mail message.
Read the associated information then fill in the mandatory parameters
and any relevant optional parameters. The parameters for each
template are identified as being required, optional, or sometimes
required. Send the completed message to
mosis@mosis.com.
Text that appears after a
REQUEST:END is ignored by the automated e-mail processor. If you
append several request messages together, be sure to remove all
REQUEST:ENDs except the one at the end of the message.
Any inclusion of a command word with a colon (as, REQUEST:) will be
parsed as a keyword command. If you have a question on message syntax
and wish to have a template fragment reviewed by the MOSIS staff, it
is important to change the colons (:) to semicolons (;) in the text.
If you do not make this change, the MOSIS software reads these as real
requests and your message, in its entirety, will not reach the MOSIS
staff.
1. ATTENTION Template
-
REQUEST: ATTENTION
DESIGN-NUMBER:
DESIGN-PASSWORD:
NET-ADDRESS:
REQUEST: END
REQUEST:ATTENTION messages are not processed by the automated system,
but instead are forwarded to a member of the MOSIS staff for handling.
-
Required parameter:
-
REQUEST: ATTENTION
-
Sometimes required:
-
DESIGN-NUMBER: required for project-specific ATTENTION requests.
-
DESIGN-PASSWORD: required for project-specific ATTENTION requests.
-
NET-ADDRESS: required if design number and design password are not
provided.
-
Put message text here, between NET-ADDRESS and REQUEST:END. Avoid
using colons (:) within the text of your message.
-
Optional parameter:
-
REQUEST: END
Anything in your message following this line will be ignored
2. NEW-PROJECT Template
-
REQUEST: NEW-PROJECT
CUSTOMER-ACCOUNT-NUMBER:
CUSTOMER-ACCOUNT-PASSWORD:
DESIGN-NAME:
DESIGN-PASSWORD:
NET-ADDRESS:
FILL-AUTHORIZED:
PHONE-NUMBER:
TECHNOLOGY-CODE:
LAMBDA:
FOUNDRY:
FAB-OPTIONS:
INTENDED-DISPOSITION:
DESIGN-KIT-VERSION:
PAD-COUNT:
DESIGN-SIZE:
PO-NUMBER:
DESCRIPTION:
QUANTITY-PACKAGED:
PACKAGE-NAME:
BONDING-DIAGRAM-SUPPLIER:
QUANTITY-UNPACKAGED:
QUANTITY-ORDERED:
ROUTING-LABEL:
QUOTE-ID:
RUN-TYPE:
IP-INCLUDED:
SPECIAL-HANDLING:
ATTENTION:
REQUEST: END
Use this request to obain a MOSIS design number for your new project:
-
Required parameters:
-
REQUEST: NEW-PROJECT
-
CUSTOMER-ACCOUNT-NUMBER:
-
CUSTOMER-ACCOUNT-PASSWORD:
-
DESIGN-NAME:
-
DESIGN-PASSWORD:
-
FILL-AUTHORIZED: Leave blank if you do not want MOSIS to fill
your design, otherwise answer "yes"
-
PHONE-NUMBER:
-
TECHNOLOGY-CODE:
-
FOUNDRY: select one: any (any foundry), Agilent (HP), AMI, AMIS,
IBM,
OMMIC, TSMC
-
PAD-COUNT:
-
DESIGN-SIZE: in microns
-
REQUEST: END
Anything in your message following this line will be ignored
-
Sometimes required:
-
LAMBDA: required only for projects with
technology
codes based on scalable design rules
(MOSIS
SCMOS); for technology codes based on non-scalable
(vendor)
rules, leave blank
-
FAB-OPTIONS: required only for TSMC 0.18 and TSMC 0.25
fabrications to specify an option not determined by the layout
-
INTENDED-DISPOSITION: required by export control regulations
-
DESIGN-KIT-VERSION: required for IBM design technologies
-
PO-NUMBER: required for commercial accounts
-
DESCRIPTION: required for all MEP submissions
-
QUANTITY-PACKAGED: required if want some parts packaged but not
all,
or if want part size contrained by a package but not packaged by MOSIS
-
PACKAGE-NAME: required if want packaged parts from MOSIS, or parts
constrained in size to be packaged elsewhere
-
BONDING-DIAGRAM: required if MOSIS is to package any parts
-
QUANTITY-UNPACKAGED: required if you want all unpackaged parts
-
QUANTITY-ORDERED: required if want more than the minimum
-
RUN-TYPE: required only for dedicated (COT) or trusted foundry runs
-
IP-INCLUDED: required only if design includes licensed
intellectual
property (for example, Artisan)
-
Optional parameters:
-
NET-ADDRESS:
-
ROUTING-LABEL:
-
QUOTE-ID: optional and only for dedicated (COT) runs
-
SPECIAL-HANDLING:
-
ATTENTION:
3. FABRICATE Template
-
You can either send your design by FTP to MOSIS,
arrange to have MOSIS retrieve your design by FTP,
or send your design to MOSIS by e-mail, whole or in
fragments.
The following is required for all FABRICATE templates if not
previously provided.
-
RUN-TYPE:
FILL-AUTHORIZED:
TECHNOLOGY-CODE:
FOUNDRY:
PAD-COUNT:
DESIGN-SIZE:
The following is required, when applicable, for all FABRICATE
templates if not previously provided.
-
LAMBDA:
DESCRIPTION:
FAB-OPTIONS:
INTENDED-DISPOSITION:
DESIGN-KIT-VERSION:
PO-NUMBER:
QUOTE-ID:
IP-INCLUDED:
Packaging information is required for all FABRICATE templates if not
previously provided.
-
QUANTITY-PACKAGED:
PACKAGE-NAME:
BONDING-DIAGRAM-SUPPLIER:
QUANTITY-UNPACKAGED:
QUANTITY-ORDERED:
3.1 To Send Your Design to MOSIS by FTP
-
REQUEST: FABRICATE
DESIGN-NUMBER:
DESIGN-PASSWORD:
LAYOUT-FORMAT:
CRC-CHECKSUM:
TOP-STRUCTURE:
ATTENTION:
LAYOUT-FTP-SEND-AUTH:
REQUEST: END
Before requesting fabrication, you must obtain a design number using
the
NEW-PROJECT request.
-
Required parameters:
-
REQUEST: FABRICATE
-
DESIGN-NUMBER:
-
DESIGN-PASSWORD:
-
LAYOUT-FORMAT: either CIF or GDS, followed by the transformations
made to the layout before it is sent. Supported transformations are
compressed, base64, uuencoded, quoted, and fragmented.
-
CRC-CHECKSUM:
-
LAYOUT-FTP-SEND-AUTH: !host!password!file!hours!
-
Sometimes required:
-
TOP-STRUCTURE: required if the format is GDS
-
Optional parameter:
-
ATTENTION:
-
REQUEST: END
Anything in your message following this line will be ignored
3.2 To Request MOSIS Retrieve Your Design by FTP
-
REQUEST: FABRICATE
DESIGN-NUMBER:
DESIGN-PASSWORD:
LAYOUT-FORMAT:
CRC-CHECKSUM:
TOP-STRUCTURE:
ATTENTION:
LAYOUT-FTP-PATH:
REQUEST: END
Before requesting fabrication, you must obtain a design number using
the
NEW-PROJECT request.
-
Required parameters:
-
REQUEST: FABRICATE
-
DESIGN-NUMBER:
-
DESIGN-PASSWORD:
-
LAYOUT-FORMAT: CIF or GDS, followed by the transformations made to
the layout before it is sent. Supported transformations are
compressed, base64, uuencoded, quoted, and fragmented.
-
CRC-CHECKSUM:
-
LAYOUT-FTP-PATH: !hostname!username!password!filename
-
Sometimes required:
-
TOP-STRUCTURE: required if the format is GDS
-
Optional parameter:
-
ATTENTION:
-
REQUEST: END
Anything in your message following this line will be ignored
3.3 To Send Your Design to MOSIS by E-mail in One Piece
-
REQUEST: FABRICATE
DESIGN-NUMBER:
DESIGN-PASSWORD:
LAYOUT-FORMAT:
CRC-CHECKSUM:
TOP-STRUCTURE:
ATTENTION:
LAYOUT:
REQUEST: END
Before requesting fabrication, you must obtain a design number using
the
NEW-PROJECT request.
-
Required parameters:
-
REQUEST: FABRICATE
-
DESIGN-NUMBER:
-
DESIGN-PASSWORD:
-
LAYOUT-FORMAT: either CIF or GDS, followed by the transformations
made to the layout before it is sent. Supported transformations are
compressed, base64, uuencoded, quoted, and fragmented.
-
CRC-CHECKSUM:
-
LAYOUT: it must be located at the bottom of the request and end
with REQUEST: END rather than simply allowing it to be
terminated by the end of the message
-
REQUEST: END
Anything in your message following this line will be ignored
-
Sometimes required:
-
TOP-STRUCTURE: required if the format is GDS
-
Optional parameter:
-
ATTENTION:
3.4 To Send Your Design to MOSIS by E-mail in Fragments
-
REQUEST: FABRICATE
DESIGN-NUMBER:
DESIGN-PASSWORD:
LAYOUT-FORMAT:
CRC-CHECKSUM:
TOP-STRUCTURE:
ATTENTION:
LAYOUT-FRAGMENT:
REQUEST: END
Before requesting fabrication, you must obtain a design number using
the
NEW-PROJECT request.
-
Required parameters:
-
REQUEST: FABRICATE
-
DESIGN-NUMBER:
-
DESIGN-PASSWORD:
-
LAYOUT-FORMAT: either CIF or GDS, followed by the transformations
made to the layout before it is sent. Since all of the fragments must
be transmited in the same format, can specify the LAYOUT-FORMAT once.
Supported transformations are compressed, base64, uuencoded, quoted,
and fragmented.
-
CRC-CHECKSUM:
-
LAYOUT-FRAGMENT: it must be located at the bottom of the request
and end with REQUEST: END rather than simply allowing it to be
terminated by the end of the message.
-
REQUEST: END
Anything in your message following this line will be ignored
-
Sometimes required:
-
TOP-STRUCTURE: required if the format is GDS
-
Optional parameter:
-
ATTENTION:
-
Sending Your Design to MOSIS by E-mail in Fragments
-
-
Divide your layout file into N fragments so that each fragment is
small enough to be handled in a single message.
-
Send N message fragments to MOSIS using the FABRICATION template
3.4 "To Send Your Design to MOSIS by E-mail in
Fragments."
The
LAYOUT-FRAGMENT parameter should look like this:
-
LAYOUT-FRAGMENT: K/N"
where N is the total number of fragments in the project file and K is
the number of the fragment. The file fragment should start on the
line following the
LAYOUT-FRAGMENT parameter.
-
MOSIS acknowledges the receipt of each fragment. When the full set
has been received, MOSIS will append the fragments together and
initiate PROJECT-CHECK.
-
You may use the
CANCEL-FABRICATION request at any time to terminate the submission
of layout fragments which will delete ALL layout for that project.
IMPORTANT NOTE:
Any submission of a layout file is terminated either explicitly by REQUEST: END, or
implicitly, when the end of the message is reached. The latter
termination typically results in the message trailer (e.g., "------"
of SNDMSG, a mailer) being appended to the end of the layout file.
This addition may be harmful at the end of LAYOUT-FRAGMENTs, which may
be in arbitrary positions in the middle of a layout file. Therefore,
all LAYOUT-FRAGMENT submissions should be explicitly terminated
REQUEST: END
4. ONE-STEP SUBMISSION Template
-
The One-Step Submission template is used to submit NEW-PROJECT and
FABRICATE requests in the same e-mail message.
4.1 To Send Your Design to MOSIS by FTP
-
REQUEST: NEW-PROJECT
CUSTOMER-ACCOUNT-NUMBER:
CUSTOMER-ACCOUNT-PASSWORD:
DESIGN-NAME:
DESIGN-PASSWORD:
PHONE-NUMBER:
DESCRIPTION:
TECHNOLOGY-CODE:
LAMBDA:
DESIGN-SIZE:
PAD-COUNT:
ROUTING-LABEL:
NET-ADDRESS:
PO-NUMBER:
SPECIAL-HANDLING:
QUOTE-ID:
RUN-TYPE:
IP-INCLUDED:
QUANTITY-PACKAGED:
PACKAGE-NAME:
BONDING-DIAGRAM-SUPPLIER:
QUANTITY-UNPACKAGED:
QUANTITY-ORDERED:
FOUNDRY:
FAB-OPTIONS:
INTENDED-DISPOSITION:
DESIGN-KIT-VERSION:
ATTENTION:
REQUEST: FABRICATE
DESIGN-NUMBER: *
DESIGN-PASSWORD:
FILL-AUTHORIZED:
CRC-CHECKSUM:
TOP-STRUCTURE:
LAYOUT-FORMAT:
LAYOUT-FTP-SEND-AUTH:
REQUEST: END
In the REQUEST:FABRICATE portion of the message you should enter an
asterisk (*) as the design number since a number has not yet been
assigned by MOSIS. Any further requests regarding this project must
include the actual design number assigned by MOSIS.
-
Required parameters:
-
REQUEST: NEW-PROJECT
-
CUSTOMER-ACCOUNT-NUMBER:
-
CUSTOMER-ACCOUNT-PASSWORD:
-
DESIGN-NAME:
-
DESIGN-PASSWORD:
-
PHONE-NUMBER:
-
TECHNOLOGY-CODE:
-
DESIGN-SIZE:
-
PAD-COUNT:
-
Sometimes required:
-
DESCRIPTION: required for all MEP submissions
-
LAMBDA: required only for projects with
technology
codes based on scalable design rules
(MOSIS
SCMOS); for technology codes based on non-scalable
(vendor)
rules, leave blank
-
PO-NUMBER: required for commercial accounts
-
IP-INCLUDED: required only if design includes licensed
intellectual
property (for example, Artisan)
-
FAB-OPTIONS: required only for TSMC 0.18 and TSMC 0.25
fabrications to specify an option not determined by the layout
-
INTENDED-DISPOSITION: required by export control regulations
-
DESIGN-KIT-VERSION: required for IBM design technologies
-
RUN-TYPE: required only for dedicated (COT) or trusted foundry
runs
-
Optional parameters:
-
ROUTING-LABEL:
-
NET-ADDRESS:
-
SPECIAL-HANDLING:
-
QUOTE-ID: optional and only for dedicated (COT) runs
-
QUANTITY-ORDERED:
-
QUANTITY-UNPACKAGED:
-
PACKAGE-NAME:
-
FOUNDRY:
-
ATTENTION:
-
Required parameters:
-
REQUEST: FABRICATE
-
DESIGN-NUMBER: Enter an asterisk (*) for the design number (real
number not yet assigned by MOSIS).
-
DESIGN-PASSWORD:
-
LAYOUT-FORMAT: either CIF or GDS, followed by the
transformations made to the layout before it is sent. Supported
transformations are compressed, base64, uuencoded, quoted, and
fragmented.
-
CRC-CHECKSUM:
-
FILL-AUTHORIZED: Leave blank if you do not want MOSIS to fill
your design, otherwise answer "yes"
-
LAYOUT-FTP-SEND-AUTH: !host!password!file!hours!
-
Sometimes required:
-
TOP-STRUCTURE: required if the format is GDS
-
Optional parameter:
-
REQUEST: END
Anything in your message following this line will be ignored
4.2 To Request MOSIS Retrieve Your Design by FTP
-
REQUEST: NEW-PROJECT
CUSTOMER-ACCOUNT-NUMBER:
CUSTOMER-ACCOUNT-PASSWORD:
DESIGN-NAME:
DESIGN-PASSWORD:
PHONE-NUMBER:
DESCRIPTION:
TECHNOLOGY-CODE:
LAMBDA:
DESIGN-SIZE:
PAD-COUNT:
ROUTING-LABEL:
NET-ADDRESS:
PO-NUMBER:
SPECIAL-HANDLING:
QUOTE-ID:
RUN-TYPE:
IP-INCLUDED:
QUANTITY-PACKAGED:
PACKAGE-NAME:
BONDING-DIAGRAM-SUPPLIER:
QUANTITY-UNPACKAGED:
QUANTITY-ORDERED:
FOUNDRY:
FAB-OPTIONS:
INTENDED-DISPOSITION:
DESIGN-KIT-VERSION:
ATTENTION:
REQUEST: FABRICATE
DESIGN-NUMBER: *
DESIGN-PASSWORD:
FILL-AUTHORIZED:
CRC-CHECKSUM:
TOP-STRUCTURE:
LAYOUT-FORMAT:
LAYOUT-FTP-PATH:
REQUEST: END
In the REQUEST:FABRICATE portion of the message you should enter an
asterisk (*) as the design number since a number has not yet been
assigned by MOSIS. Any further requests regarding this project must
include the actual design number assigned by MOSIS.
-
Required parameters:
-
REQUEST: NEW-PROJECT
-
CUSTOMER-ACCOUNT-NUMBER:
-
CUSTOMER-ACCOUNT-PASSWORD:
-
DESIGN-NAME:
-
DESIGN-PASSWORD:
-
PHONE-NUMBER:
-
TECHNOLOGY-CODE:
-
DESIGN-SIZE:
-
PAD-COUNT:
-
Sometimes required:
-
DESCRIPTION: required for all MEP submissions
-
LAMBDA: required only for projects with
technology
codes based on scalable design rules
(MOSIS
SCMOS); for technology codes based on non-scalable
(vendor)
rules, leave blank
-
PO-NUMBER: required for commercial accounts
-
IP-INCLUDED: required only if design includes licensed
intellectual
property (for example, Artisan)
-
FAB-OPTIONS: required only for TSMC 0.18 and TSMC 0.25
fabrications to specify an option not determined by the layout
-
INTENDED-DISPOSITION: required by export control regulations
-
DESIGN-KIT-VERSION: required for IBM design technologies
-
RUN-TYPE: required only for dedicated (COT) or trusted foundry
runs
-
Optional parameters:
-
ROUTING-LABEL:
-
NET-ADDRESS:
-
SPECIAL-HANDLING:
-
QUOTE-ID: optional and only for dedicated (COT) runs
-
QUANTITY-ORDERED:
-
QUANTITY-UNPACKAGED:
-
PACKAGE-NAME:
-
FOUNDRY:
-
ATTENTION:
-
Required parameters:
-
REQUEST: FABRICATE
-
DESIGN-NUMBER: Enter an asterisk (*) for the design number (real
number not yet assigned by MOSIS).
-
DESIGN-PASSWORD:
-
LAYOUT-FORMAT: either CIF or GDS, followed by the
transformations made to the layout before it is sent. Supported
transformations are compressed, base64, uuencoded, quoted, and
fragmented.
-
CRC-CHECKSUM:
-
FILL-AUTHORIZED: Leave blank if you do not want MOSIS to fill
your design, otherwise answer "yes"
-
LAYOUT-FTP-PATH: hostname!username!password!filename
-
Sometimes required:
-
TOP-STRUCTURE: required if the format is GDS
-
Optional parameter:
-
REQUEST: END
Anything in your message following this line will be ignored
4.3 To Send Your Design to MOSIS by E-mail in One Piece
Message
-
REQUEST: NEW-PROJECT
CUSTOMER-ACCOUNT-NUMBER:
CUSTOMER-ACCOUNT-PASSWORD:
DESIGN-NAME:
DESIGN-PASSWORD:
PHONE-NUMBER:
DESCRIPTION:
TECHNOLOGY-CODE:
LAMBDA:
DESIGN-SIZE:
PAD-COUNT:
ROUTING-LABEL:
NET-ADDRESS:
PO-NUMBER:
SPECIAL-HANDLING:
QUOTE-ID:
RUN-TYPE:
IP-INCLUDED:
QUANTITY-PACKAGED:
PACKAGE-NAME:
BONDING-DIAGRAM-SUPPLIER:
QUANTITY-UNPACKAGED:
QUANTITY-ORDERED:
FOUNDRY:
FAB-OPTIONS:
INTENDED-DISPOSITION:
DESIGN-KIT-VERSION:
ATTENTION:
REQUEST: FABRICATE
DESIGN-NUMBER: *
DESIGN-PASSWORD:
FILL-AUTHORIZED:
CRC-CHECKSUM:
TOP-STRUCTURE:
LAYOUT-FORMAT:
LAYOUT:
REQUEST: END
In the REQUEST:FABRICATE portion of the message you should enter an
asterisk (*) as the design number since a number has not yet been
assigned by MOSIS. Any further requests regarding this project must
include the actual design number assigned by MOSIS.
-
Required parameters:
-
REQUEST: NEW-PROJECT
-
CUSTOMER-ACCOUNT-NUMBER:
-
CUSTOMER-ACCOUNT-PASSWORD:
-
DESIGN-NAME:
-
DESIGN-PASSWORD:
-
PHONE-NUMBER:
-
TECHNOLOGY-CODE:
-
DESIGN-SIZE:
-
PAD-COUNT:
-
Sometimes required:
-
DESCRIPTION: required for all MEP submissions
-
LAMBDA: required only for projects with
technology
codes based on scalable design rules
(MOSIS
SCMOS); for technology codes based on non-scalable
(vendor)
rules, leave blank
-
PO-NUMBER: required for commercial accounts
-
IP-INCLUDED: required only if design includes licensed
intellectual
property (for example, Artisan)
-
FAB-OPTIONS: required only for TSMC 0.18 and TSMC 0.25
fabrications to specify an option not determined by the layout
-
INTENDED-DISPOSITION: required by export control regulations
-
DESIGN-KIT-VERSION: required for IBM design technologies
-
RUN-TYPE: required only for dedicated (COT) or trusted foundry
runs
-
Optional parameters:
-
ROUTING-LABEL:
-
NET-ADDRESS:
-
SPECIAL-HANDLING:
-
QUOTE-ID: optional and only for dedicated (COT) runs
-
QUANTITY-ORDERED:
-
QUANTITY-UNPACKAGED:
-
PACKAGE-NAME:
-
FOUNDRY:
-
ATTENTION:
-
Required parameters:
-
REQUEST: FABRICATE
-
DESIGN-NUMBER: Enter an asterisk (*) for the design number (real
number not yet assigned by MOSIS).
-
DESIGN-PASSWORD:
-
LAYOUT-FORMAT: either CIF or GDS, followed by the
transformations made to the layout before it is sent. Supported
transformations are compressed, base64, uuencoded, quoted, and
fragmented.
-
CRC-CHECKSUM:
-
FILL-AUTHORIZED: Leave blank if you do not want MOSIS to fill
your design, otherwise answer "yes"
-
LAYOUT: it must be located at the bottom of the request and end
with REQUEST: END rather than simply allowing it to be terminated by
the end of the message
-
REQUEST: END
Anything in your message following this line will be ignored
-
Sometimes required:
-
TOP-STRUCTURE: required if the format is GDS
5. UPDATE Template
-
REQUEST: UPDATE
DESIGN-NUMBER:
DESIGN-PASSWORD:
DESIGN-NAME:
DESCRIPTION:
TECHNOLOGY-CODE:
LAMBDA:
RUN-TYPE:
IP-INCLUDED:
FILL-AUTHORIZED:
FOUNDRY:
FAB-OPTIONS:
INTENDED-DISPOSITION:
DESIGN-KIT-VERSION:
LAYOUT-FORMAT:
TOP-STRUCTURE:
DESIGN-SIZE:
PAD-COUNT:
QUANTITY-PACKAGED:
PACKAGE-NAME:
BONDING-DIAGRAM-SUPPLIER:
QUANTITY-UNPACKAGED:
QUANTITY-ORDERED:
PO-NUMBER:
QUOTE-ID:
PHONE-NUMBER:
NET-ADDRESS:
ROUTING-LABEL:
SPECIAL-HANDLING:
REQUEST: END
You can use this request to change certain parameters you submitted to
MOSIS for your design. The UPDATE request does NOT affect your layout
file nor allow you to provide a new layout file.
-
Required parameters:
-
REQUEST: UPDATE
-
DESIGN-NUMBER:
-
DESIGN-PASSWORD:
-
Parameters you can add or update:
-
DESIGN-NAME:
-
DESCRIPTION: required for all MEP submissions
-
TECHNOLOGY-CODE:
-
LAMBDA: required only for projects with
technology
codes based on scalable design rules
(MOSIS
SCMOS); for technology codes based on non-scalable
(vendor)
rules, leave blank
-
RUN-TYPE: required only for dedicated (COT) or trusted foundry
runs
-
IP-INCLUDED: required only if design includes licensed
intellectual
property (for example, Artisan)
-
FILL-AUTHORIZED: to change a previous request, answer "no" if you
do not want MOSIS to fill your design, answer "yes" if you do want
MOSIS to fill your design
-
FOUNDRY:
-
FAB-OPTIONS: required only for TSMC 0.18 and TSMC 0.25
fabrications to specify an option not determined by the layout; update
will replace not add to any previous requests; "none" will remove all
requested options
-
INTENDED-DISPOSITION: required by export control regulations
-
DESIGN-KIT-VERSION: required for IBM design technologies
-
LAYOUT-FORMAT: either CIF or GDS, followed by the
transformations made to the layout before it is sent. Supported
transformations are compressed, base64, uuencoded, quoted, and
fragmented.
-
TOP-STRUCTURE: required if the format is GDS
-
DESIGN-SIZE:
-
PAD-COUNT:
-
QUANTITY-PACKAGED: required if want some parts packaged but not
all,
or if want part size contrained by a package but not packaged by MOSIS
-
PACKAGE-NAME: required if want packaged parts from MOSIS, or parts
constrained in size to be packaged elsewhere
-
BONDING-DIAGRAM: required if MOSIS is to package any parts
-
QUANTITY-UNPACKAGED: required if you want all unpackaged parts
-
QUANTITY-ORDERED: required if want more than the minimum
-
PO-NUMBER: required for commercial accounts
-
QUOTE-ID: optional and only for dedicated (COT) runs
-
PHONE-NUMBER:
-
NET-ADDRESS:
-
ROUTING-LABEL:
-
SPECIAL-HANDLING:
-
Optional parameters:
-
REQUEST: END
Anything in your message following this line will be ignored
6. CANCEL-FABRICATION Template
-
REQUEST: CANCEL-FABRICATION
DESIGN-NUMBER:
DESIGN-PASSWORD:
REQUEST: END
This request cancels a previously requested fabrication of a project,
but retains the design number for future use. Use this request when
you want to submit a new layout file under an existing design number.
Note that this request does NOT cancel the project. You should submit
a separate
CANCEL-PROJECT request if you don't plan to submit a new FABRICATE
request for this design number.
All parameters are required.
7. CANCEL-PROJECT Template
-
REQUEST: CANCEL-PROJECT
DESIGN-NUMBER:
DESIGN-PASSWORD:
REQUEST: END
Use this request to complete cancel a project for which you have
obtained a design number.
All parameters are required.
8. STATUS Template
-
You can request the status of a project, either by its 5-digit MOSIS
design number, or by its run number when it goes into fabrication.
8.1 Request Project Status
-
REQUEST: STATUS
DESIGN-NUMBER:
DESIGN-PASSWORD:
REQUEST: END
Use this request to obtain status of a project using the 5-digit MOSIS
Design Number. For more detailed information, see the
Project Status Documentation.
All parameters are required.
8.2 Request Run Status
-
REQUEST: INFORMATION
FILE:
REQUEST: END
Use this request to track the progress of the run containing your
design.
When your design is accepted on a run, you'll receive by e-mail a
confirmation with your unique fabrication id. The first four
characters identify the run.
-
All parameters are required
-
FILE: the file name format is run_number.sts. For run T16W,
request the file T16W.STS
9. REPORT Template
-
REQUEST: REPORT
DESIGN-NUMBER:
DESIGN-PASSWORD:
FAB-ID:
DESIGN-TYPE:
SUBMITTER:
EMAIL-ADDRESS:
NUMBER-PARTS-RECEIVED:
NUMBER-PARTS-TESTED:
NUMBER-PARTS-FUNCTIONAL:
PART-SPEED:
FAILURE-CAUSES:
COMMENTS:
PROJECT-URL:
REQUEST: END
Use this template to send a report after you receive and test your
parts.
You must send a separate report for each fabrication of your project.
(In other words, you must send a separate report for each Fabrication
ID assigned by MOSIS). The Fabrication ID is a 6 character ID like
"T16WAB". Each report should clearly identify both the Project
ID (like "T16W") and the Fab-ID (like "AB") of the project.
-
Required parameters:
-
REQUEST: REPORT
-
DESIGN-NUMBER:
-
DESIGN-PASSWORD:
-
DESIGN-TYPE:
-
SUBMITTER:
-
EMAIL-ADDRESS:
-
NUMBER-PARTS-RECEIVED:
-
NUMBER-PARTS-TESTED:
-
NUMBER-PARTS-FUNCTIONAL:
-
REPORT: must be the last parameter in the message before
REQUEST:END
-
Provide additional information about your design, your test results,
and other observations. Details of differences between simulated and
measured circuit performance, and concrete, specific descriptions of
any perceived problems with the quality of the wafer fabrication or
the packaging are helpful.
-
REQUEST: END
Anything in your message following this line will be ignored
-
Sometimes required:
-
FAB-ID: required if design fabbed more than once
-
PART-SPEED: speed of parts, if applicable
-
FAILURE-CAUSES:
Replace this text with the best information
you have about why the parts failed or did
not perform as expected.
-
Optional parameter:
-
ATTENTION:
PROJECT-URL:
|
Related Links
Fabrication Schedule
Customer Support
MOSIS Products
|
|
|
